On Tue, Jun 07, 2005 at 09:47:47AM -0500, [email protected] wrote:
> > Why not fix the firmware_class.c code now? :)
> I am working on a solution for this; so yes, I will submit a patch to
> enhance firmware_class.c code.
Good.
> Mean while the driver sent earlier is tested and working on current
> version of 2.6 kernel and we have tested it with various distros based
> on 2.6 kernel. Changing the kernel and making the driver dependent on
> the new code will make the driver not work on the current kernels which
> the users have.
Drivers are tightly bound to kernel versions. Nothing new there.
> This will make driver non functional on current 2.6 kernels and will be
> an issue if users don't want to upgrade their kernels but just want the
> driver to update BIOS.
Then persuade the distros to accept your current version. That's not
our issue :)
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
