List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
I agree that extra useflags arent such a good idea ;)
Since the "Configure" of pcmcia-cs is not autogenerated but handmade, and
the kernel configuration is allready read there, the hisax support of the interesting cards should
be easy to check, so the ebuild will only do an extra patch.
So my original question has been answered by the code already :)
However its the question if it would be better to provide a patch "with" the sources of
these *_cs.c pcmcia client drivers, that could break with the hisax part of the driver,
or copy the kernel _cs.c files of this clients, which could possibly break with the pcmcia part.
I personally would prefer trying to copy & compile the sources from the kernel dir, to fit against
latest patches to the isdn and HiSax subsystem.
I dont think the pcmcia system in the 2.4 kernel would be changed to a level where
a _cs.c file from the kernel wouldnt compile with the pcmcia_cs pcmcia sub-system anymore,
since that would affect the cardmgr and such, which comes always with pcmcia-cs
and would have to comply with kernel-pcmcia in that case, too.
It is theoretically possible, but a change to the isdn system or comunication between the
hisax part and the _cs part of the same card driver is more likely, and would break _cs parts
supplied by a patch to pcmcia_cs directly.
The alternative would be to provide almost the whole isdn or at least hisax support with
pcmcia-cs like its done with WLAN card support.
but since only 3 of the about 2 dozen ISDN cards supported by HiSax are PCMCIAs,
this wouldnt be such a good idea i think.
firstname.lastname@example.org mailing list