On Sun, 2013-03-17 at 16:24 +0100, Camaleón wrote:
> El 2013-03-17 a las 14:58 +0000, Ben Hutchings escribió:
>
> > On Sun, 2013-03-17 at 15:46 +0100, Camaleón wrote:
>
> (...)
>
> > > Using Debian's stock network driver is not an option for me (full report
> > > available here²) so I have to try with the latests drivers but now that
> > > "compat-drivers" are compiled the generated modules cannot be loaded.
> > >
> > > Is there any by-pass for this?
> > >
> > > ¹http://marc.info/?t=136351034300002&r=1&w=2
> > > ²http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664767
> >
> > Talk to the compat-drivers developers.
>
> To be sincere, I don't think that's a user's role.
>
> I don't know what's going on with these drivers but if they are not
> supported by Debian at all it would be better for all of us (plain
> users and developers) to simply say it so to avoid wasting time and
> resources.
I would like to support them, in fact more than that I would like to
integrate them into official packages. But there is no way we can
support an OOT module that defines symbols that we might need to add for
our own backports. As it is 'compat' will ironically cause
incompatibility with Debian's own kernel upgrades.
Compat developers: please add a prefix (not 'compat', that one's already
taken!) to all the symbols exported by the 'compat' module. Just
#define'ing the function/variable name before declaring them should
avoid the need for any changes to the drivers using it.
Ben.
--
Ben Hutchings
Usenet is essentially a HUGE group of people passing notes in class.
- Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'
Attachment:
signature.asc
Description: This is a digitally signed message part