In general, just adding the device id to a driver in order to enable
it for a new device is not sufficient. They may (in most cases, will)
be additional logic that is needed in the driver to correctly enable
the new device. If this is the case, I'd expect the patched driver to
fail on open even with the 2.6 kernel.
ganesh.
On 4/25/05, Torben Mathiasen <[email protected]> wrote:
> On Mon, Apr 25 2005, Alan Cox wrote:
> > Try with 2.6.x - I'm not sure the 64bit cleanness stuff ever all got
> > into the 2.4 driver version.
>
> Yeah the 2.6 version is your best bet. Allthough, I haven't tried it on an
> Alpha in a long time.
>
> BTW. I'm not maintaining the driver anymore. Samuel Chessman ([email protected])
> took over maintainership, but I'm not sure if he's still active.
>
> Torben
> -
> 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/
>
-
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]
