* Eric W Biederman <ebi...@ln...> [020821 20:12]:
> > Aside from the legal / copyright issues, a few technical points spring
> > to mind:
> >
> > 1. The nVidia .o file is 20kB in size - around 4-5 times the size of most
> > of the Etherboot drivers. This might be enough to prevent it working
> > in 5.0.x (AFAICT, the memory-map changes in the 5.1.x branch will fix
> > this anyway).
>
> This assumes the appropriate virt_to_bus, bus_to_virt and ioremap calls
> are being made. Otherwise it try reading and writing to the wrong
> registers.
Would a driver working in Linux not always require the virt_to_bus
address shifting?
> > 3. As others have said, don't bother faking a kernel network API - just
> > take the skeleton Etherboot driver in skel.c and fill out the gaps
> > between that and the nVidia .o file.
Not faking the kernel api, but faking the api that nvidia uses
in it's wrapper and on the other side, implementing a suitable etherboot
api grip.
Best regards,
Stefan
--
The x86 isn't all that complex - it just doesn't make a lot of
sense. -- Mike Johnson, Leader of 80x86 Design at AMD
Microprocessor Report (1994)
|