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: Mon, 14 Apr 2003 15:53:14 +0200 [thread overview]
Message-ID: <3E8AE87E00006D87@ocpmta2.freegates.net> (raw)
In-Reply-To: <1050320386.25353.11.camel@dhcp22.swansea.linux.org.uk>
>
>On Llu, 2003-04-14 at 13:13, Joel Soete wrote:
>> +#if defined(__hppa__) && defined(CONFIG_SUPERIO)
>> +#include <asm/superio.h>
>> +#endif
>> +
>
>Please keep superio out of generic drivers
>
>
>> if (!using_inta)
>> +#if defined(__hppa__) && defined(CONFIG_SUPERIO)
>> + hwif->irq = superio_get_ide_irq(); /* legacy mode */
>> +#else
>> hwif->irq = hwif->channel ? 15 : 14; /* legacy mode */
>> +#endif
>> else if (!hwif->irq && hwif->mate && hwif->mate->irq)
>> hwif->irq = hwif->mate->irq; /* share IRQ with mate */
>
>Ughh. Ok this needs tackling in a more general way. get_legacy_irq(0/1)
>perhaps. This isnt the only port we need to sort out.
>
>Ok suppose you added superio.h to include/asm-parisc/ide.h and added
>ide_get_legacy(int n) [n=0/1] for interfaces. I can do the same for the
>other ports (return 14+n) and it will stay clean in 2.4 and 2.5
>
>
>> (dev->class & 0x80))) {
>> - unsigned long dma_base = ide_get_or_set_dma_base(hwif);
>> + u32 dma_base = ide_get_or_set_dma_base(hwif);
>
>Thats reverting a fix. dma_base must be unsigned long for 64bit
>platforms. Looks just like a merge error.
Sorry note a merge error but well a revert because I encounter a problem
in a previous merge. I have to review,
Thanks for advises,
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 prev parent reply other threads:[~2003-04-14 13:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030410155223.GA5254@dsl2.external.hp.com>
2003-04-11 5:40 ` [parisc-linux] parisc-linux.org kernel 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 [this message]
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-18 8:17 Joel Soete
2003-04-18 11:40 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 16:44 Joel Soete
2003-04-16 16:50 ` Matthew Wilcox
2003-04-16 10:13 Joel Soete
2003-04-16 11:06 ` Alan Cox
2003-04-14 11:52 Joel Soete
2003-04-14 11:54 ` Matthew Wilcox
2003-04-14 12:53 ` Joel Soete
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=3E8AE87E00006D87@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