From: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>
To: Torben Mathiasen <torben.mathiasen@hp.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Atro.Tossavainen@helsinki.fi, torben.mathiasen@compaq.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux kernel TI TLAN driver
Date: Mon, 25 Apr 2005 09:30:12 -0700 [thread overview]
Message-ID: <5fc59ff3050425093012ab23b2@mail.gmail.com> (raw)
In-Reply-To: <20050425135603.GD7617@linux2>
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 <torben.mathiasen@hp.com> 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 (chessman@tux.org)
> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2005-04-25 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 8:00 Linux kernel TI TLAN driver Atro Tossavainen
2005-04-22 8:53 ` P Lavin
2005-04-25 11:24 ` Alan Cox
2005-04-25 13:56 ` Torben Mathiasen
2005-04-25 16:30 ` Ganesh Venkatesan [this message]
2005-04-25 17:12 ` Torben Mathiasen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5fc59ff3050425093012ab23b2@mail.gmail.com \
--to=ganesh.venkatesan@gmail.com \
--cc=Atro.Tossavainen@helsinki.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torben.mathiasen@compaq.com \
--cc=torben.mathiasen@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox