Date: Wed, 10 May 1995 00:16:28 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: hm@altona.hamburg.com Cc: freebsd-hackers@FreeBSD.org Subject: Re: A question of downloading device drivers Message-ID: <199505100716.AAA07061@gndrsh.aac.dev.com> In-Reply-To: <m0s95LA-0002OfC@ernie.altona.hamburg.com> from "Hellmuth Michaelis" at May 10, 95 08:33:48 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > >From the keyboard of Rodney W. Grimes: > > > > I think you mean the EXOS 205T boards. Down loading via ioctl() > > > sucks (I know; I happen to be doing it for LKM). > > > > The EXOS 205T is an IBM/PC board, the EXOS board I am referring to > > is a Unibus board. And I was wrong, it is the Interlan board, not > > the Excelan board :-). > > Are the ioctl's necessary for downloading implemented in the ethernet > driver's ioctl 'space' or does it use a separate character device just > for downloading ? I suggest you go look in the 4.4BSD Lite sources, mine are off line right now and I don't like to do other folks leg work. The pointer is missing from the above quoted text, but in the original I did point to the 4.4 sources. > > > > Really, it should be done with kernel level vnode I/O, just like the > > > UFS disk quotas. > > Do you mean that the device driver code should access a file in the > filesystem directly ? Terry will have to answer that, it was his assertion. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505100716.AAA07061>