From: "Ralph Blach" <rblach@intrex.net>
To: Eugene Surovegin <ebs@ebshome.net>,
<linuxppc-embedded@lists.linuxppc.org>,
Xupei Liang <tliang@yahoo.com>
Subject: Re: IDE driver support in PPC440
Date: Wed, 14 May 2003 12:09:05 -0400 [thread overview]
Message-ID: <200305141209.AA2923954376@intrex.net> (raw)
I am using the MontaVista 2.1 port and the Promise IDE works perfectly. I just plugged it in and it just ran.
Chip
---------- Original Message ----------------------------------
From: Xupei Liang <tliang@yahoo.com>
Date: Wed, 14 May 2003 08:20:11 -0700 (PDT)
>
>Hi, Eugene,
>
>The IRQ7 is setup as level trigger and active low.
>
>I think what happened is that when the ISR is
>serving the first interrupt, which is external
>interrupt 7 (number 50), it is interrupted again.
>This time, ppc405_pic_get_irq() returns irq 64 because
>the routine knows that all interrupts have been
>disabled (I have looked at UIC_ER0 and UIC_ER1
>and verified that is the case). So the question is,
>if all interrupts are disabled, why the code is stuck
>inside the ISR?
>
>I am using the lastest 2.4.19 code.
>
>Thank you for your help again.
>
>Regards,
>
>Terry L.
>
>
>--- Eugene Surovegin <ebs@ebshome.net> wrote:
>>
>> At 10:15 PM 5/13/2003, Xupei Liang wrote:
>>
>>
>> >I am working on a PPC440 board that supports
>> >a PCI-IDE device, and I am experiencing an
>> >interrupt handling problem.
>> >
>> >The PCI-IDE controller uses External Interrupt 7
>> and
>> >the controller interrupt line is wired to the
>> >processor directly. When the IDE device is
>> >being initialized, I can see that the interrupt
>> >goes off. But the code is stuck in the
>> >ISR and can not get out. Here are the screen
>> >debug messages:
>> >
>> ><Linux booting up>
>> >ide1: CMD649 Bus-Master DMA disabled (BIOS)
>> >disabling irq 50 defensively
>> >ppc405_uic_disable - irq 50 word 1 bit 0x12
>> >hda: SanDisk SDCFB-128, ATA DISK drive
>> >ppc405_uic_enable - irq 50 word 1 bit 0x12
>> >ppc405_uic_enable - irq 50 word 1 bit 0x12
>> >ide0 at 0x2000-0x2007,0x3002 on irq 50
>> >hda: 250880 sectors (128 MB) w/1KiB Cache,
>> >CHS=980/8/32
>> >Partition check:
>> > hda:ppc405_pic_get_irq - irq 50 bit 0x2000
>> >ppc405_uic_disable_and_ack - irq 50 word 1 bit 0x12
>> >ppc405_pic_get_irq - irq 64 bit 0x0
>> >ppc405_pic_get_irq - irq 64 bit 0x0
>> >-------------
>>
>> Well, "irq 64" bothers me.
>> You shouldn't see this message. Real external
>> interrupts are in the range 0-63
>>
>> Please, check that you are using latest code from
>> 2.4 devel tree
>> (in particular file arch/ppc/kernel/ppc4xx_pic.c)
>>
>> BTW, how did you setup trigger and polarity settings
>> for IRQ7 ?
>>
>> Eugene.
>>
>>
>>
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-05-14 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 16:09 Ralph Blach [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 5:15 IDE driver support in PPC440 Xupei Liang
2003-05-14 6:56 ` Eugene Surovegin
2003-05-14 15:20 ` Xupei Liang
2003-05-14 16:57 ` Eugene Surovegin
2003-05-15 14:56 ` Xupei Liang
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=200305141209.AA2923954376@intrex.net \
--to=rblach@intrex.net \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tliang@yahoo.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;
as well as URLs for NNTP newsgroup(s).