public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: "Welch, Martyn (GE EntSol,
	Intelligent Platforms)" <martyn.welch@gefanuc.com>
Cc: Rajat Jain <Rajat.Jain@infogain.com>,
	kernelnewbies@nl.linux.org, linux-newbie@vger.kernel.org
Subject: Re: PCI interrupt queries
Date: Thu, 21 Aug 2008 13:10:52 +0200	[thread overview]
Message-ID: <48AD4D3C.3010703@keyaccess.nl> (raw)
In-Reply-To: <1CADFA951940554D86FBD8B24BBFF3A001E7390E@LONMLVEM08.e2k.ad.ge.com>

On 21-08-08 11:31, Welch, Martyn (GE EntSol, Intelligent Platforms) wrote:

> Rajat Jain wrote:

>> OK. But who does it in an embedded environment (PPC for eg) where 
>> there is no POST software. The first piece of code that gets
>> executed is U-boot and then the kernel. So who writes the LINE
>> value into the config space?
> 
> U-boot does. There is a fairly standardised way to connect PCI interrupt
> lines, especially for PCI slots where various cards can be plugged in:

How peculiar, a boot loader doing hardware programming...

Rene.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2008-08-21 11:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19  5:11 PCI interrupt queries Rajat Jain
2008-08-19 20:34 ` Rene Herman
2008-08-20  4:50   ` Rajat Jain
2008-08-20 18:04     ` Rene Herman
2008-08-21  9:31     ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-08-21 11:10       ` Rene Herman [this message]
2008-08-21 11:12         ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-08-21 17:14       ` Om
2008-08-21  5:42 ` Greg KH

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=48AD4D3C.3010703@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=Rajat.Jain@infogain.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=martyn.welch@gefanuc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox