> (I'm trying to get a D-Link gigabit card working, and the r8169 driver
> supports it but doesn't have its PCI-ID in it, so won't load. The above
> hack swaps out an ID I don't need and puts in the one I do so that it'll
> load. Changing the driver source and recompiling is the "correct" way to
> do this but the system in question doesn't have a compiler.)
Perl, of course!
perl -pi.$$ -e 's,oldthing,newthing,g' driver.ko
The better solution is to just build the driver on another system
that DOES have a compiler and copy it to the system you intend to run it
on. This is how kernels and drivers are built in cross-compile situations,
Canadian Cross and so on. Works like a charm. How do you think all of
those complicated Linux applications and drivers make their way onto Linux
PDAs? You think they're compiling them on 300Mhz/400Mhz PDA processors
(and killing the flash by doing so)? Nope, they're built elsewhere and
rolled into the image or scp/cp/rsync/ftp'd into place.
> I can do this a number of other ways (like pulling the file onto another
> system that has a binary editor on it) so this is more for my own
> curiosity than anything else.
vi -b
David A. Desrosiers
Linux on Power Developer Program Manager
[EMAIL PROTECTED]
_______________________________________________
Peterboro mailing list
Peterboro@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/peterboro
