casper....@sun.com wrote: > >> There does have the requirement to read files in the kernel. >> >> We're working on a 10Gb Ethernet driver and we want to let the driver >> update the firmware on-the-fly if needed when the driver is loaded. >> Save the firmware image in a separate file and let the driver read it >> with kobj_open_file() should be an option. But kobj_open_file() is not a >> stable interface. So what's the best practice for the task like this? > > Well, if you're the driver in on, then the fact that kobj_open_file() > isn't stable doesn't matter. If you're in ON, when they change it they > need to change all consumers of that interface.
Yes, it's in ON, so the stability of the interface is not a big issue. I remembered there were once some discussion to make it a public interface. But I'm not sure where the firmware image file should locate. There is no guide document to consult. > > Apart from kobj_open_file(), we've also used specific daemon which will > download the file through a ioctl; that is what we do for the SPARC > graphics hardware. What's the exact driver? We may get some idea from the implementation. Thanks, Lucy > > Casper > > _______________________________________________ > opensolaris-code mailing list > opensolaris-code@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/opensolaris-code > _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
