On Mon, May 26, 2003 at 10:52:04PM -0400, Soren Andersen wrote:
>
> So part of what I am saying is that the absence of monetary renumeration
> alone does not make Saints or Martyrs of some sort out of developers who
> program "outside of their regular working hours" on Open-Source
> projects.
Ok, I've resisted responding to this thread long enough. First off, a
few comments:
- I do not know of any Linux usb developers who get paid to do this,
myself included.
- Programmers primarily like to write code. Since they are doing this
because they want to, the fact that they don't write any pretty user
documentation is no problem at all. If others view this as a
problem, it is their problem, not the original developer's problem.
That being said, the current Linux USB Guide has been a wonderful
document, and I sincerely thank Brad for writing it and maintaining it
over time. I refer people to it almost every day, and it answers their
questions quite well.
Now I get a _lot_ of user email about usb stuff on Linux. Those emails
usually fall into the following categories:
- "I plugged my device in, now how do I use it?" This is a general
Linux question, as the same thing could be said for any kind of
device. The Linux USB Guide helps out just fine here for pointing
people which device node to connect to, and they are off and
running.
- "My USB device isn't assigned an address". This is a ACPI/PCI
interrupt routing issue that isn't the USB project's problem. I
point them at the "noapic" command line argument, and the ACPI
project, nothing much we can do there.
- "My new wizzy USB device isn't supported by Linux." This is the
hardest, as Linux doesn't support a lot of different USB devices,
because we don't have the specs for the devices. This includes the
wide range of usb-storage devices that decide to ignore the specs
and do their own thing...
So, in summary, the current Linux USB Guide works for the first question
(which is the majority of my email.) The second question isn't a USB
problem at all, and the third can't really be fixed by any changes to
the USB Guide, right?
So if you think there is some more documentation that needs to be
written, by all means, write away. Personally I don't see much need for
any more, and I am one of the main people helping Linux USB users out
every day for the past few years.
Oh, as for the programming documentation, check out the 2.5 kernel docs,
by running 'make psdocs'. It's quite good these days, thanks to the
effort of David Brownell. Also, any discrepancies noticed in
Documentation/usb/* would be nice to know, as they should be fixed up if
there are any.
Thanks again Brad for that Guide, it's a life saver for me.
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
