All of lore.kernel.org
 help / color / mirror / Atom feed
From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: Porting MIPS IRQ handler to ARM
Date: Tue, 01 Sep 2015 11:07:44 -0700	[thread overview]
Message-ID: <55E5E970.90801@gmail.com> (raw)
In-Reply-To: <55E5E70D.4060006@free.fr>

On 01/09/15 10:57, Mason wrote:
> M?ns Rullg?rd wrote:
> 
>> Mason wrote:
>>
>>> I'm trying to port to my ARM platform: IRQ handling code written for MIPS.
>>> https://github.com/mansr/linux-tangox/blob/master/drivers/irqchip/irq-tangox.c
>>
>> Go get the latest version of that file.  It should work on ARM now.
> 
> It would probably have taken me days to figure out I could just delete
> the arch-dependent code. Linux internals are so hard to grok... <sigh>
> 
> Would you like me to ask if they can send you a dev board? :-)
> 
> By the way, it seems the generic UART driver does not use interrupts,
> which would explain why the console works despite my busted device tree.
> Does that mean that the driver polls? (I'll take a closer look tomorrow.)

Kernel console is buffer and polled, user-space (tty) console uses
interrupts.
-- 
Florian

  reply	other threads:[~2015-09-01 18:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 16:14 Porting MIPS IRQ handler to ARM Mason
2015-09-01 16:58 ` Florian Fainelli
2015-09-02 16:25   ` Mason
2015-09-02 17:17     ` Måns Rullgård
2015-09-02 18:01       ` Mason
2015-09-04 16:13         ` Mason
2015-09-04 16:36           ` Måns Rullgård
2015-09-04 17:46             ` Mason
2015-09-04 21:49               ` Måns Rullgård
2015-09-04 16:37           ` Måns Rullgård
2015-09-04 21:20             ` Matthias Brugger
2015-09-01 17:07 ` Måns Rullgård
2015-09-01 17:57   ` Mason
2015-09-01 18:07     ` Florian Fainelli [this message]
2015-09-01 19:01       ` Mason

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=55E5E970.90801@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.