|
From: Eric W B. <ebi...@ln...> - 2002-08-22 13:28:25
|
Stefan Reinauer <st...@su...> writes: > * 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? There is a fairly big difference between virt_to_bus, and pci_alloc_consistent. A modern Linux driver will use pci_alloc_consistent. Plus if the abstraction is poor nvidia could be making assumptions about how Linux implements virt_to_bus which is totally different from the etherboot implementation. The reason etherboot can get away with virt_to_bus is that when it is ported I can essentially do pci_alloc_consistent on the entire etherboot image. At least that is the plan. Eric |
