From: "Joel Soete" <jsoe0708@tiscali.be>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Grant Grundler" <grundler@parisc-linux.org>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] parisc-linux.org kernel
Date: Wed, 16 Apr 2003 12:13:38 +0200 [thread overview]
Message-ID: <3E9BA3A600000AF6@ocpmta2.freegates.net> (raw)
>-- Original Message --
>Subject: Re: [parisc-linux] parisc-linux.org kernel
>From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>To: Joel Soete <jsoe0708@tiscali.be>
>Cc: Grant Grundler <grundler@parisc-linux.org>,
> parisc-linux@lists.parisc-linux.org
>Date: 15 Apr 2003 16:54:32 +0100
>
>
>On Maw, 2003-04-15 at 17:32, Joel Soete wrote:
>
>> >ide_get_legacy(int n) [n=0/1] for interfaces.
>>
>> And so I still have to add
>> #if defined(CONFIG_SUPERIO)
>> # define ide_get_legacy(x) superio_get_ide_irq()
>> #else
>> # define ide_get_legacy(x) ... (still have to find what)
well: clearer this morning, it would just have to become
# define ide_get_legacy((x)) (x)?15:14
>> #endif
>
>What do you need to know if the legacy irq is to come from superio.
If I well understand the question: nothing because superio_get_ide_irq()
is defined in arch/parisc/kernel/superio.c as:
...
int
superio_get_ide_irq(void)
{
if (sio_dev.irq_region)
return sio_dev.irq_region->data.irqbase + IDE_IRQ;
else
return 0;
}
sio_dev being a global var:
...
static struct superio_device sio_dev = {
iosapic_irq: -1
};
which is define in include/asm-parisc/superio.h as:
...
struct superio_device {
u16 fdc_base;
u16 sp1_base;
u16 sp2_base;
u16 pp_base;
u16 acpi_base;
int iosapic_irq;
int iosapic_irq_enabled;
struct irq_region *irq_region;
struct pci_dev *lio_pdev; /* pci device for legacy IO fn */
};
...
>Should be we be asking ide_get_legacy(struct pci_device *pdev) ?
IMHO it would be difficult this way; what do you thing?
>
>I just want to understand this so I (or you) do it right
>
You have certainly more experience and a broader view (over different platform)
than I (up to you)
Is this actually help?
Joel
---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be
next reply other threads:[~2003-04-16 10:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 10:13 Joel Soete [this message]
2003-04-16 11:06 ` [parisc-linux] parisc-linux.org kernel Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-04-18 8:17 Joel Soete
2003-04-18 11:40 ` Joel Soete
2003-04-16 16:44 Joel Soete
2003-04-16 16:50 ` Matthew Wilcox
2003-04-14 11:52 Joel Soete
2003-04-14 11:54 ` Matthew Wilcox
2003-04-14 12:53 ` Joel Soete
[not found] <20030410155223.GA5254@dsl2.external.hp.com>
2003-04-11 5:40 ` Joel Soete
2003-04-11 9:41 ` Joel Soete
2003-04-11 15:58 ` Grant Grundler
2003-04-12 20:30 ` Joel Soete
2003-04-14 12:13 ` Joel Soete
2003-04-14 11:39 ` Alan Cox
2003-04-14 13:53 ` Joel Soete
2003-04-14 15:42 ` Joel Soete
2003-04-15 16:32 ` Joel Soete
2003-04-15 15:54 ` Alan Cox
2003-04-15 16:41 ` Randolph Chung
2003-04-15 16:47 ` Matthew Wilcox
2003-04-15 16:52 ` Joel Soete
2003-04-14 14:18 ` Michael Wood
2003-04-09 7:36 Berthold Gunreben
2003-04-08 16:53 Alexander Gabert
2003-04-08 16:58 ` Matthew Wilcox
2003-04-08 17:06 ` Alexander Gabert
2003-04-08 17:08 ` Matthew Wilcox
2003-04-09 5:49 ` Grant Grundler
2003-04-09 7:54 ` Alexander Gabert
2003-04-09 15:47 ` Grant Grundler
2003-04-09 17:23 ` pageexec
2003-04-09 17:40 ` Matthew Wilcox
2003-04-09 18:20 ` pageexec
2003-04-09 17:48 ` Matthew Wilcox
2003-04-10 5:50 ` Grant Grundler
2003-04-10 11:19 ` Matthew Wilcox
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=3E9BA3A600000AF6@ocpmta2.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.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