mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robert Bisping <rbisping@mindspring.com>
To: Emiliano Gabrielli <Emiliano.Gabrielli@roma2.infn.it>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: yenta-cardbus IRQ0
Date: Mon, 3 Feb 2003 20:03:41 -0500	[thread overview]
Message-ID: <E18frZq-0003TC-00@barry.mail.mindspring.net> (raw)
In-Reply-To: <200302031116.37035.gabrielli@roma2.infn.it>

On Monday 03 February 2003 05:16, you wrote:
> On 03:16, domenica 2 febbraio 2003, Robert Bisping wrote:
> > > >> last month and it keeps coming up with IRQ0 and telling me it cant
> > > >> find a  irq for pin A. what would be causing this and how do I
> > > >> correct it i have  already tried APCI and it does not work on my
> > > >> laptop so that is no help. I  have compiled SMP into the kernel
> > > >> though I dont have a dual processor (of  course) to gain the added
> > > >> functionality. I have recompiled my kernel about  150 times with
> > > >> different setting hoping it might just be a conflict in the  kernel
> > > >> with no luck.  I looked at the yenta driver it's self and noticed
> > > >> that  it accepts IRQ0 as a valid irq but that appears to mean no irq
> > > >> at all. which  config file would i use to force it to set a irq?
> > > >>
> > > >> > Thanx for any assistanc you might give
> > > >>
> > > >> plz send an lspci -vv -xxx -s *your dev*
> > > >>
> > > >> what kernel are you using ?
> > > >
> > > > i am using 2.4.18 and here is lspci
> > >
> > > uhmm, 1th try to upgrade to a newer one, then I experienced the same
> > > problem with a custom board... the problem was triggered by the Base
> > > Address too high:
> > >
> > >   Region 0: Memory at 10812000 (32-bit, non-prefetchable) [size=4K]
> > >
> > > moving id_sel (in the PCI core of the board) in order to obtain a lower
> > > bar all worked.
> > >
> > >
> > > BTW, has anybody there ever heared about such a costraint in the PCI
> > > specification ?? Why I got this strange behaviour ???
> >
> > ok, can you give me some more specifics? i.e how do i do that or what
> > howto/man etc. (not the kernel part the id_sel part) thanx
>
> I think you can't do that if you are not able to put your hand in the HW.
> There's nothing you can do from linux, that I know...
>
> You can take a look to the PCI specification, but i don't think it will aid
> you so much...
when I reformated my drive for linux i lost the ibm configuration utilities 
for windows and havent been able to get them back any other suggestions or 
how do i get to the bios froma floppy with a thinkpad 760ed.

thanx

      reply	other threads:[~2003-02-04  0:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31  9:45 Robert Bisping
2003-01-31 13:50 ` Emiliano Gabrielli
2003-01-31 21:58   ` Robert Bisping
2003-02-01 10:33     ` Emiliano Gabrielli
2003-02-02  2:16       ` Robert Bisping
2003-02-03 10:16         ` Emiliano Gabrielli
2003-02-04  1:03           ` Robert Bisping [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=E18frZq-0003TC-00@barry.mail.mindspring.net \
    --to=rbisping@mindspring.com \
    --cc=Emiliano.Gabrielli@roma2.infn.it \
    --cc=linux-kernel@vger.kernel.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®