From: Samuel Ortiz <samuel@sortiz.org>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-kernel@vger.kernel.org,
Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
ambx1@neo.rr.com, bjorn.helgaas@hp.com,
Linus Walleij <linus.walleij@ericsson.com>
Subject: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip
Date: Mon, 4 Jun 2007 23:44:18 +0300 [thread overview]
Message-ID: <20070604204418.GA4214@sortiz.org> (raw)
In-Reply-To: <200706040634.01622.arvidjaar@mail.ru>
(Adding Linus Walleij, who wrote part of the smsc driver, to Cc:)
On Mon, Jun 04, 2007 at 06:33:56AM +0400, Andrey Borzenkov wrote:
> On Monday 04 June 2007, Samuel Ortiz wrote:
> > It seems that PnP tells us that the FIR port is at 0x2e8 while we're
> > expecting it at 0x2f8.
> > Could you apply this patch and then send me a dmesg dump of the
> > smsc-ircc initialisation ?
> >
>
> here is dmesg:
>
> Detected unconfigured Toshiba laptop with ALi ISA bridge SMSC IrDA chip,
> pre-configuring device.
> Activated ALi 1533 ISA bridge port 0x02e8.
> Activated ALi 1533 ISA bridge port 0x02f8.
> pnp: Device 00:0a activated.
> smsc_ircc_pnp_probe(): fir 0x2e8 sir 0x100 dma 1 irq 5
Ok, FIR and SIR are definitey mixed up. So, now could you please try Bjorn's
patch ? I wonder if the curent code (without PnP) enables 0x2f8 as the SIR
port through the preconfiguration code...
Cheers,
Samuel.
> High: 0xef, Chip 0x1
> smsc_ircc_present(), addr 0x02e8 - no device found!
> pnp: Device 00:0a disabled.
>
> And here is what PnP tells us:
> {pts/1}% cat /sys/bus/pnp/devices/00:0a/options
> port 0x100-0x130, align 0xf, size 0x8, 16-bit address decoding
> irq 3,4,5,6,7,10,11 High-Edge
> dma 1,2,3 16-bit compatible
> Dependent: 01 - Priority acceptable
> port 0x3f8-0x3f8, align 0x0, size 0x8, 16-bit address decoding
> Dependent: 02 - Priority acceptable
> port 0x2e8-0x2e8, align 0x0, size 0x8, 16-bit address decoding
> Dependent: 03 - Priority acceptable
> port 0x2f8-0x2f8, align 0x0, size 0x8, 16-bit address decoding
> Dependent: 04 - Priority acceptable
> port 0x3e8-0x3e8, align 0x0, size 0x8, 16-bit address decoding
> {pts/1}% cat /sys/bus/pnp/devices/00:0a/resources
> state = disabled
> {pts/1}% sudo sh -c 'echo activate > /sys/bus/pnp/devices/00:0a/resources'
> {pts/1}% cat /sys/bus/pnp/devices/00:0a/resources
> state = active
> io 0x100-0x107
> io 0x2e8-0x2ef
> irq 5
> dma 1
>
> -andrey
>
> > Cheers,
> > Samuel.
> >
> >
> > diff --git a/drivers/net/irda/smsc-ircc2.c b/drivers/net/irda/smsc-ircc2.c
> > index 9043bf4..d1d46a6 100644
> > --- a/drivers/net/irda/smsc-ircc2.c
> > +++ b/drivers/net/irda/smsc-ircc2.c
> > @@ -391,6 +391,9 @@ static int __init smsc_ircc_pnp_probe(struct pnp_dev
> > *dev, dma = pnp_dma(dev, 0);
> > irq = pnp_irq(dev, 0);
> >
> > + printk("%s(): fir 0x%x sir 0x%x dma %d irq %d\n",
> > + __FUNCTION__, firbase, sirbase, dma, irq);
> > +
> > if (smsc_ircc_open(firbase, sirbase, dma, irq))
> > return -ENODEV;
> >
> > @@ -655,6 +658,7 @@ static int smsc_ircc_present(unsigned int fir_base,
> > unsigned int sir_base) irq = (config & IRCC_INTERFACE_IRQ_MASK) >> 4;
> >
> > if (high != 0x10 || low != 0xb8 || (chip != 0xf1 && chip != 0xf2)) {
> > + printk("High: 0x%x, Chip 0x%x\n", high, chip);
> > IRDA_WARNING("%s(), addr 0x%04x - no device found!\n",
> > __FUNCTION__, fir_base);
> > goto out3;
>
>
next prev parent reply other threads:[~2007-06-04 20:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 8:00 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip Andrey Borzenkov
2007-06-03 8:16 ` Andrey Borzenkov
2007-06-03 23:10 ` Samuel Ortiz
2007-06-04 2:33 ` Andrey Borzenkov
2007-06-04 20:44 ` Samuel Ortiz [this message]
2007-06-05 3:10 ` Andrey Borzenkov
2007-06-05 7:18 ` Linus Walleij (LD/EAB)
2007-06-05 7:57 ` Samuel Ortiz
2007-06-05 11:57 ` Linus Walleij (LD/EAB)
2007-06-05 13:04 ` Samuel Ortiz
2007-06-05 23:23 ` Bjorn Helgaas
2007-06-06 3:29 ` Andrey Borzenkov
2007-06-06 19:09 ` Bjorn Helgaas
2007-06-06 20:45 ` Andrey Borzenkov
2007-06-07 15:52 ` Bjorn Helgaas
2007-06-07 20:47 ` Samuel Ortiz
2007-06-10 6:47 ` Andrey Borzenkov
2007-06-10 21:03 ` Bjorn Helgaas
2007-06-11 14:04 ` Andrey Borzenkov
2007-06-14 21:30 ` Bjorn Helgaas
2007-06-15 13:44 ` Andrey Borzenkov
2007-06-15 15:19 ` Bjorn Helgaas
2007-06-16 16:38 ` Andrey Borzenkov
2007-06-19 23:31 ` Bjorn Helgaas
2007-06-28 3:56 ` Bjorn Helgaas
2007-06-30 2:41 ` Bjorn Helgaas
2007-06-30 7:16 ` Andrey Borzenkov
2007-06-30 11:45 ` Bjorn Helgaas
2007-06-30 14:47 ` Andrey Borzenkov
2007-06-30 21:13 ` Andrey Borzenkov
2007-07-01 3:30 ` Bjorn Helgaas
2007-07-01 7:08 ` Andrey Borzenkov
2007-07-01 13:57 ` Bjorn Helgaas
2007-08-11 18:39 ` Andrey Borzenkov
2007-08-13 16:09 ` Bjorn Helgaas
2007-08-13 17:39 ` Peter Stuge
2007-08-18 6:59 ` Andrey Borzenkov
2007-07-01 0:01 ` Michal Piotrowski
2007-07-01 0:04 ` Michal Piotrowski
2007-06-07 18:34 ` Bjorn Helgaas
2007-06-08 5:24 ` Andrey Borzenkov
2007-06-10 8:03 ` Andrey Borzenkov
2007-06-10 20:04 ` Bjorn Helgaas
2007-06-07 12:23 ` Linus Walleij (LD/EAB)
2007-06-07 15:44 ` Bjorn Helgaas
2007-06-05 12:06 ` Linus Walleij (LD/EAB)
2007-06-04 16:34 ` Bjorn Helgaas
2007-06-05 3:08 ` Andrey Borzenkov
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=20070604204418.GA4214@sortiz.org \
--to=samuel@sortiz.org \
--cc=ambx1@neo.rr.com \
--cc=arvidjaar@mail.ru \
--cc=bjorn.helgaas@hp.com \
--cc=linus.walleij@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.