> > OK, fair enough, I forgot about tg3. But on the other hand, you
> > wrote
> > it without docs, actually _in spite of_ Broadcom, right?
> > Which I think makes my point that documentation is neither necessary
> > nor sufficient for a good Linux driver. Documentation helps, but if
> > no one competent cares about the device then the driver won't get
> > written. On the other hand, if the device is important enough, the
> > driver will get written without documentation or vendor support.
>
> That's your point?? I thought your point was (quoting your words)
>
> > it's a
> > bit disingenous to suggest that all a company has to do to get a
> > driver written and supported is throw some documentation over the
> > wall. And it's crazy to suggest that the driver will work on every
> > platform and be supported by enterprise distros.
>
> To repeat -- that's how most Linux drivers have been written,
> /particularly/ the ones used most by users of enterprise distros.
I thought you wrote tg3 without docs and without help from Broadcom?
To repeat, my point is that the drivers used most by users of
enterprise distros will get written with or without vendor docs or
help. Drivers for hardware that only a few people care about probably
won't be written and definitely won't be maintained by volunteers even
if the vendor publishes docs. And I think that's pretty much what I
said in both of the paragraphs you quoted above.
- R.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
