mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Filo <krzysztof.gorgolewski@gmail.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de,
	linux-pci@atrey.karlin.mff.cuni.cz,
	linux-pcmcia@lists.infradead.org
Subject: Re: PROBLEM: Paceblade Pacebook no irq for TI yenta PCMCIA - PCI related
Date: Thu, 3 Nov 2005 22:14:51 -0800	[thread overview]
Message-ID: <20051103221451.2799eb17.akpm@osdl.org> (raw)
In-Reply-To: <fda8dbc60510291430w30d8ffdfo80c45595778f938@mail.gmail.com>

Filo <krzysztof.gorgolewski@gmail.com> wrote:
>
>  I'm trying to get my PCMCIA port running on my pacebook tablet. I'm
>  using 2.6.* kernel (actually 2.6.13-rc4-mm1 but I also tried 2.6.12)
>  and during initialization of yenta_socket I get this message:
> 
>  Yenta: Routing CardBus interrupts to PCI
>  Yenta TI: socket 0000:00:05.0, mfunc 0x01021c02, devctl 0x64
>  Yenta TI: socket 0000:00:05.0 probing PCI interrupt failed, trying to fix
>  Yenta TI: socket 0000:00:05.0 no PCI interrupts. Fish. Please report.
>  Yenta: no PCI IRQ, CardBus support disabled for this socket.
>  Yenta: check your BIOS CardBus, BIOS IRQ or ACPI settings.
>  Yenta: ISA IRQ mask 0x0ad8, PCI irq 0
> 
>  It seam that Yenta cant get information about the irq's from the PCI.
>  It's not an ACPI issue because I did not compile it (it's broken on my
>  tablet). I'm quite confused what to do now. Any help (even a dirty
>  hack) would be appreciated.

Did the machine work OK under any earlier kernels?  2.4?  If so, which?

Did you try enabling ACPI under the 2.6 kernel, because that might be the
fix.  If ACPI fails then please raise a separate report for that
(preferably at bugzilla.kernel.org).

Thanks.


      reply	other threads:[~2005-11-04  6:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 21:30 Filo
2005-11-04  6:14 ` Andrew Morton [this message]

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=20051103221451.2799eb17.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=krzysztof.gorgolewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linux-pcmcia@lists.infradead.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

all inboxes | Powered by JetHome®