public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Ritz <daniel.ritz@gmx.ch>
To: Pavel Roskin <proski@gnu.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	linux-pcmcia <linux-pcmcia@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] yenta: irq-routing for TI bridges - take 2
Date: Wed, 25 Feb 2004 21:03:47 +0100	[thread overview]
Message-ID: <200402252103.48739.daniel.ritz@gmx.ch> (raw)
In-Reply-To: <Pine.LNX.4.58.0402250148080.2144@portland.hansa.lan>

On Wednesday 25 February 2004 07:55, Pavel Roskin wrote:
> On Wed, 25 Feb 2004, Daniel Ritz wrote:
> 
> > hi
> >
> > the last patch was bad...chaning stuff it shouldn't on TI125x, 145x...
> >
> > another try...comments?
> > couldn't find datasheets for 1210, 1220, 1250 so i'm not quite sure about them....
> 
> http://www.mit.edu/afs/sipb/contrib/doc/specs/ic/bridge/

thanks...i looked at the 1220 datasheet and it seems the chip is sane enough
so no special case like the 1250 is needed. the 1210 should be just the same but
with only one slot.

> 
> > compile tested (my TI works, so no difference there)
> 
> Works for me.  yenta_socket is compiled into the kernel.  Two cards:  TI
> 1221 with 2 slots (no fixup needed) and TI 1410 that needs it.
> 

nice to hear it works.

> 
> Yenta: CardBus bridge found at 0000:00:08.0 [133f:1233]
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: mfunc 0cc07d92, devctl 60

mfunc0 is inta, mfunc1 is irq9, mfunc2 is activity led, mfunc3 is irq7,
mfunc4 GPI3, mfunc5 is the other led, mfunc6 is irq12...

this would give you irq7,9,12 but device control says parallel PCI only..

> Yenta: ISA IRQ mask 0x0000, PCI irq 5
> Socket status: 30000006
> Yenta: CardBus bridge found at 0000:00:08.1 [133f:1233]
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: mfunc 0cc07d92, devctl 60
> Yenta: ISA IRQ mask 0x0000, PCI irq 5
> Socket status: 30000006
> Yenta: CardBus bridge found at 0000:00:0a.0 [0000:0000]
> Yenta: Enabling burst memory read transactions
> Yenta: Using CSCINT to route CSC interrupts to PCI
> Yenta: Routing CardBus interrupts to PCI
> Yenta TI: mfunc 00000000, devctl 66

that's just an uninitialized ti1410. so we're using PCI


> Yenta TI: changing mfunc to 00001000
> Yenta TI: falling back to PCI interrupts
> Yenta TI: changing mfunc to 00001002
> Yenta: ISA IRQ mask 0x0000, PCI irq 12
> 
> $ cat /proc/interrupts
>            CPU0
>   0:     664717          XT-PIC  timer
>   1:       1530          XT-PIC  i8042
>   2:          0          XT-PIC  cascade
>   5:          3          XT-PIC  yenta, yenta, orinoco_cs
>   7:          0          XT-PIC  acpi
>   8:          4          XT-PIC  rtc
>  10:       1502          XT-PIC  uhci_hcd, uhci_hcd
>  11:         46          XT-PIC  eth0
>  12:          3          XT-PIC  yenta, VIA686A, orinoco_cs
>  14:      36354          XT-PIC  ide0
>  15:         21          XT-PIC  ide1
> NMI:          0
> ERR:          0
> 
> -- 
> Regards,
> Pavel Roskin
> 

rgds
-daniel 


  reply	other threads:[~2004-02-25 20:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-23 23:33 [PATCH] yenta: irq-routing for TI bridges Daniel Ritz
2004-02-24  0:00 ` Russell King
2004-02-24  0:32   ` Daniel Ritz
2004-02-24  1:06     ` Pavel Roskin
2004-02-24 11:59       ` Daniel Ritz
2004-02-24 12:40         ` Russell King
2004-02-24 15:23           ` Daniel Ritz
2004-02-24 23:26             ` [PATCH] yenta: irq-routing for TI bridges - take 2 Daniel Ritz
2004-02-25  6:55               ` Pavel Roskin
2004-02-25 20:03                 ` Daniel Ritz [this message]
2004-02-25 21:20                   ` Pavel Roskin
2004-02-25 23:01                     ` Daniel Ritz
2004-02-24 16:38           ` [PATCH] yenta: irq-routing for TI bridges David Hinds
2004-02-24  0:46   ` Pavel Roskin
2004-02-24 12:44     ` Russell King

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