From: Roland Tollenaar <rwatollenaar@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: Xenomai-help@domain.hid
Subject: Re: [Xenomai-help] acpi and irq
Date: Sun, 09 Sep 2007 18:47:06 +0200 [thread overview]
Message-ID: <46E4238A.7010108@domain.hid> (raw)
In-Reply-To: <18148.5503.43798.880010@domain.hid>
Hi Giles,
Thanks. I thought I had already tried all combinations but I was wrong.
Your advice moved me to mess about a little more. All seems to be
working now. Phew....
If you would care to comment, is this not a bit of a black art? It seems
super primitive to have to mess about with PCI slots until there is no
conflict. Why is this not taken care of more decently by firmware / OS?
No rebuke to anyone (I'm too clueless myself) just very curious. Is it
so hard or are there fundamental complexities in automatically sorting
this out? untracktable problem? This question obviously has no relation
to xenomai. My apologies but it may be ignored of course. :)
Kind regards
Roland.
Gilles Chanteperdrix wrote:
> Roland Tollenaar wrote:
> > Hi,
> >
> > I am having trouble with shared irq on two NIC's that I am trying to
> > sort out.
> >
> > Googling for solutions I notice that acpi has a lot to do with this. I
> > recall somewhere that ACPI support can be disabled in the config when
> > patching with xenomai. I was jsut wondering whether this can be related
> > to the problem I have?
>
> I'd say you are confusion ACPI and APIC, and yes, enabling the APIC
> makes more IRQs available, so maybe this could help Linux avoiding IRQ
> sharing. Changing cards from slot usually also helps.
>
prev parent reply other threads:[~2007-09-09 16:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 14:02 [Xenomai-help] acpi and irq Roland Tollenaar
2007-09-09 15:47 ` Gilles Chanteperdrix
2007-09-09 16:47 ` Roland Tollenaar [this message]
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=46E4238A.7010108@domain.hid \
--to=rwatollenaar@domain.hid \
--cc=Xenomai-help@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=rolandtollenaar@domain.hid \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.