Bug#703142: compatibility with alx ?
El 2013-03-17 a las 18:17 +0000, Ben Hutchings escribió:
> On Sun, 2013-03-17 at 16:24 +0100, Camaleón wrote:
> > > 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.
Understood. Thanks for the explanation, I was not aware of this.
> 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.
As per your last suggestion I posted to the kernel backports mailing
list and it seems they already did something with the name, let's see if
I can get more info from them.
¹http://marc.info/?l=linux-backports&m=136354363318801&w=2
Greetings,
--
Camaleón
Reply to: