public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-pcmcia <linux-pcmcia@lists.infradead.org>,
	Daniel Ritz <daniel.ritz@gmx.ch>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6] ToPIC specific init for yenta_socket
Date: Wed, 6 Aug 2003 20:32:17 +0100	[thread overview]
Message-ID: <20030806203217.F16116@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.56.0308061452310.3849@marabou.research.att.com>; from proski@gnu.org on Wed, Aug 06, 2003 at 03:07:21PM -0400

On Wed, Aug 06, 2003 at 03:07:21PM -0400, Pavel Roskin wrote:
> I read the PCMCIA list, but not LKML, and I have no idea what problems you
> are talking about.  Could you please explain of give a pointer to a
> previous post?  I could cross-check the problem against plx9052 driver.

It's fairly complex.  Let's just summerise it as "yenta texas instruments
IRQ routing fucked up" 8)  The chip has a bunch of registers to control
what signals get routed to which physical pins, and it seems that between
June 2002 and today, some bad changes happened.  I'm currently trying to
track down each one, but, as there have been several levels of patching
going on, it isn't simple.

> The same is done for TI and Ricoh bridges.  Just search the sources for
> "socket->socket.ops->init".  You may have a good reason to be unhappy, but
> coherent code is normally easier to fix than a bunch of different hacks.

Yep, and I'm going to fix them as part of my present work.

Think about what happens to ->init with the current system when you
have two different cardbus controllers in the same machine.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-08-06 19:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06 18:25 [PATCH 2.6] ToPIC specific init for yenta_socket Daniel Ritz
2003-08-06 18:44 ` Russell King
2003-08-06 19:07   ` Pavel Roskin
2003-08-06 19:32     ` Russell King [this message]
2003-08-06 20:39       ` Pavel Roskin
2003-08-06 22:23         ` TI yenta-alikes (was: ToPIC specific init for yenta_socket) Tim Small
2003-08-07  4:01           ` Pavel Roskin
2003-08-07  9:02             ` Russell King
2003-08-07 12:18               ` Alan Cox
2003-08-07 13:02                 ` TI yenta-alikes Tim Small
2003-08-07 13:16                   ` Russell King
2003-08-07 14:00                     ` Alan Cox
2003-08-07 14:38                       ` Russell King
2003-08-07 14:49                     ` Tim Small
2003-08-07 13:12                 ` TI yenta-alikes (was: ToPIC specific init for yenta_socket) Russell King
2003-08-07  9:18             ` TI yenta-alikes Tim Small
2003-08-06 20:50   ` [PATCH 2.6] ToPIC specific init for yenta_socket Daniel Ritz

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=20030806203217.F16116@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=daniel.ritz@gmx.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=proski@gnu.org \
    /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