From: Jeff Garzik <[email protected]>
Date: Sun, 01 Oct 2006 23:54:42 -0400
> Jan Engelhardt wrote:
> >> Tons of ISDN drivers cast pointers to/from 32-bit values, which just
> >> won't work on 64-bit.
> >
> > Should not that be fixed instead of restricting isdn to 32bit?
>
> It hasn't been fixed in many years, and I don't see anyone stepping up
> to the plate, even with my current trolling... :)
>
> > Though this is probably the best temporary workaround until someone can
> > fix up all the "tons".
>
> I have a better workaround, I think.
I totally agree with Jeff. The ISDN layer is effectively unmaintained
and the vast majority of the ISDN work that does actually occur is
done out-of-tree.
If someone cares enough about the ISDN layer, they can make changes
after Jeff's goes in to reduce the protection to a per-driver basis.
But right now, blocking this whole unmaintained pile of poo on 64-bit
is the best starting point.
We're talking about effectively an 8 year old code base that hasn't
been touched much at all during that time. Let's be honest about the
situation. The only subsystem that is more unmaintained and gathering
dust is probably the ftape layer :-)
-
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]
