All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: David Jez <dave.jez@seznam.cz>
Cc: Martin Mares <mj@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: PCI & IRQ problems on TI Extensa 600CD
Date: Fri, 29 Oct 2004 05:50:08 -0400	[thread overview]
Message-ID: <41821250.70502@verizon.net> (raw)
In-Reply-To: <20041029081848.GA5240@stud.fit.vutbr.cz>

David Jez wrote:
>   Hi all,
> 
>   Last night i solved this problem. It cause by crippled PCI chipset
> parody called ALi and his perverse undocumented "features". I think that
> use ISA bridge as IRQ router if we haven't any router is guite good idea.
>   Everythink with this patch works fine even though i have different irq in
> win. See attached logs.
>   Jim, can you try this patch please? I assume that you have some kind
> of ALi chipset too. Maybe this solves your problem too.
>   Martin, Marcelo, please aply :-).
> 
> PS: is here anybody who have relevant datascheet?
> 
>   Regards,
> 
> 

Naah.  I have a piix chipset.  My problem (per David Hinds) is that my laptop is 
even more b0rken than yours - IBM never hooked up the PCI INTx lines on the TI 
1130.  My laptop never worked with Cardbus stuff - even in Windows.

He reccommended the external pcmcia_cs package for my system - there's a dummy_cs 
module in there (2.4 only, though) that should fix my problem.

Thanks,

Jim

  reply	other threads:[~2004-10-29  9:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23 14:29 PCI & IRQ problems on TI Extensa 600CD David Jez
2004-10-23 19:53 ` Jim Nelson
2004-10-25 16:19   ` David Jez
2004-10-29  8:18     ` David Jez
2004-10-29  9:50       ` Jim Nelson [this message]
2004-10-29 10:14         ` David Jez
2004-11-01  8:42         ` David Jez
2004-11-01 12:59           ` Jim Nelson
2004-11-01 20:27             ` David Jez
2004-11-02 14:15               ` Jim Nelson
2004-11-02 16:24                 ` Jim Nelson

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=41821250.70502@verizon.net \
    --to=james4765@verizon.net \
    --cc=dave.jez@seznam.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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.