RFC: i386: kill !4KSTACKS
Quoted 5 lines
The NdisWrapper FAQ already tells you that you need a patch for some of the binary-only Windows drivers that require more than 8kB stacks.
And the fact that NdisWrapper is mostly working hinders the development of open source drivers for this hardware.
If the hardware manufacturer won't give you the spec's then writing a driver is going to be pretty difficult, if not impossible. Reverse-engineering may be possible, but still....
I believe it's the lack of spec's, rather than the existence of ndiswrapper and driverloader, that hinder driver development.
-Alex
I code, therefore I am
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Quoted 6 lines · Alex Davis
Quoted 5 lines
The NdisWrapper FAQ already tells you that you need a patch for some of the binary-only Windows drivers that require more than 8kB stacks.
And the fact that NdisWrapper is mostly working hinders the development of open source drivers for this hardware.
Quoted 6 lines
If the hardware manufacturer won't give you the spec's then writing a driver is going to be pretty difficult, if not impossible. Reverse-engineering may be possible, but still....
I believe it's the lack of spec's, rather than the existence of ndiswrapper and driverloader, that hinder driver development.
How do you put pressure on hardware manufacturers for getting them to release the specs?
If they are able to write "supported by Linux" on their products anyway because there's a driver that runs under NdisWrapper?
Or if people return/don't buy the hardware because of missing Linux support reducing the revenue of the hardware manufacturer by some $$ ?
Quoted 1 line
-Alex
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 5 lines · Adrian Bunk
How do you put pressure on hardware manufacturers for getting them to release the specs?
If they are able to write "supported by Linux" on their products anyway because there's a driver that runs under NdisWrapper?
that's specious... they can put "supported by Linux" on their products by supplying a binary-only driver too... ndiswrapper is orthogonal to that problem.
on a tangent... has there been any further research/work on page clustering? wli's patches haven't been updated in a while... it's another way to supply larger stacks. (hell with 16KiB "pages" i'd be stoked to "waste" the bottom 4KiB of each stack with an unmapped page to ensure overflow is detected.)
-dean