From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: David Hinds <dhinds@sonic.net>,
daniel.ritz@gmx.ch, linux-kernel@vger.kernel.org
Subject: Re: REMINDER: 2.4.25 and 2.6.x yenta detection issue
Date: Fri, 19 Mar 2004 21:07:20 +0000 [thread overview]
Message-ID: <20040319210720.J14431@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0403191509280.2227-100000@dmt.cyclades>; from marcelo.tosatti@cyclades.com on Fri, Mar 19, 2004 at 03:14:54PM -0300
On Fri, Mar 19, 2004 at 03:14:54PM -0300, Marcelo Tosatti wrote:
> It seems the problem reported by Silla Rizzoli is still present in 2.6.x
> and 2.4.25 (both include the voltage interrogation patch by rmk).
>
> Daniel Ritz made some efforts to fix it, but did not seem to get it right.
And that effort is still going on. Daniel and Pavel have been trying
to find a good algorithm for detecting and fixing misconfigured TI
interrupt routing, and this effort is still on-going.
What would be useful is if Silla could test some of Daniel's patches
and provide feedback.
The latest 2.6 patch from Daniel is at:
http://ritz.dnsalias.org/linux/pcmcia-ti-routing-9.patch
and I'll ask that feedback is sent to linux-pcmcia and not as a reply
to this message (I'm just monitoring what's going on at present.)
Essentially, this patch needs to be well tested before it goes into
mainline.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-03-19 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 18:14 REMINDER: 2.4.25 and 2.6.x yenta detection issue Marcelo Tosatti
2004-03-19 21:07 ` Russell King [this message]
2004-03-21 0:51 ` Daniel Ritz
2004-04-28 19:54 ` Jonathan Sambrook
2004-04-28 21:10 ` Daniel Ritz
2004-04-29 17:37 ` Jonathan Sambrook
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=20040319210720.J14431@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=daniel.ritz@gmx.ch \
--cc=dhinds@sonic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.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