From: David Brownell <david-b@pacbell.net>
To: linux-omap-open-source@linux.omap.com
Subject: Re: CONFIG_PREEMPT_RT patch on Apollon (OMAP2)
Date: Thu, 30 Nov 2006 13:35:23 -0800 [thread overview]
Message-ID: <200611301335.23815.david-b@pacbell.net> (raw)
In-Reply-To: <456B3802.1000101@gmail.com>
On Monday 27 November 2006 11:09 am, Dirk Behme wrote:
> > 1. ethernet flags
> > - After change from IRQF_RISING to IRQF_HIGH in recent OMAP2 patch. it occurs the GPIO bug message in line 1005.
> > So I reverted IRQF_RISING as before. then it's working.
>
> Maybe David has an idea here? [1]
No. H4 with NFSroot and current GIT works fine for me; that
uses IRQF_TRIGGER_LOW.
The "best" solution would of course be passing the flags in
the IRQ resource, but that'd be more invasive to smc91x and
(eventually) the board init code. platform_get_irq() doesn't
pass those flags along.
- Dave
next prev parent reply other threads:[~2006-11-30 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 6:59 CONFIG_PREEMPT_RT patch on Apollon (OMAP2) Kyungmin Park
2006-11-27 19:09 ` Dirk Behme
2006-11-30 21:35 ` David Brownell [this message]
2006-11-28 6:14 ` Dirk Behme
2006-11-28 7:08 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2006-11-28 8:09 Kyungmin Park
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=200611301335.23815.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.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 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.