> On Sun, 23 Jan 2000, Mike Smith wrote:
>
> > > I can't agree with Mike Smith that reading the code is adequate. It
> > > certainly doesn't apply to newcomers, but it doesn't even apply to
> > > seasoned hackers like Mike: the BSD style doesn't provide for adequate
> > > comments, and so what you see from the code is mainly tactics, not
> > > strategy.
> >
> > You miss my point; you don't want to be writing a driver until you know
> > what you're doing. Documentation on an OS' driver interface won't teach
> > you that; it's something that's really only ever gleaned from experience.
>
> The problem is, you can't even find what the interfaces are. Reading the
> code isn't very useful if you can't even find the right place to start
> from. At least the interface points could be listed, so that someone
> would know where to begin.
Listing the interface points won't help unless you know which ones are
relevant to what you're trying to do. I say it again; first you need to
know how to write a device driver, then you need to know what the
available tools are to get the job done. Having only the latter does
not help at all with the former.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message