Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Erik Rull <erik.rull@rdsoftware.de>
To: linux-ide@vger.kernel.org
Subject: IRQ 15  not assigned, but still unable to use it - in MSDOS it works
Date: Wed, 16 Jun 2010 13:30:19 +0200	[thread overview]
Message-ID: <4C18B5CB.4060707@rdsoftware.de> (raw)

Hi all,

I've worked a lot on bringing the IRQ 15 to work for my embedded system but 
it still fails.

My kernel is the 2.6.29.4 - I've already updated from 2.6.23.3 because 
there were some bugs in some ata drivers.
My system is a embedded system with Intel ATOM CPU and Intel 965 chipset.
I need to access some very old ISA-Bus boards. Before I used a Pentium-M 
Board that worked perfect.
The new board seems to have problems disabling the IRQ 15 in linux. BIOS 
has IRQ 15 reserved for legacy hardware and the IDE port behind it is 
disabled - so IRQ15 should be really free.
The 2.6.23.3 found an IDE device and said afterwards that it is disabled 
but kept the resources assigned without releasing them - so I was not able 
to use the IRQ15 with my own software.
With the 2.6.29.4 I don't get this any longer but the IRQ15 doesn't work 
either. Other interrupts are fine (5 or 10) but they are already used by 
other hardware components.
Now the interesting part: in MSDOS I'm able to see the IRQ15 from the ISA 
board as a source....

So I think that linux somewhere takes the IRQ15 and does not allow me to 
use it - and IRQ sharing seems not to be possible in this case.

I need some ideas where to continue my search - I think that it is 
somewhere in the libata that blocks this interrupt. /proc/interrupts shows 
up no interrupt neither that #15 is used.

Any ideas?

If you need more information please let me know.

Thanks a lot!

Best regards,

Erik

             reply	other threads:[~2010-06-16 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 11:30 Erik Rull [this message]
2010-06-18  3:01 ` IRQ 15 not assigned, but still unable to use it - in MSDOS it works Robert Hancock
2010-06-19 11:25   ` Erik Rull

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=4C18B5CB.4060707@rdsoftware.de \
    --to=erik.rull@rdsoftware.de \
    --cc=linux-ide@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