From: Antony Pavlov <antonynpavlov@gmail.com>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: barebox@lists.infradead.org
Subject: Re: Barebox newbie questions : arch/arm/{plat, mach} split and interrupts
Date: Mon, 14 Nov 2011 12:34:50 +0300 [thread overview]
Message-ID: <CAA4bVAGvndiAjGmNGNeJGm=R_t+fm6krwqVHjhqBftBm-wP6Cg@mail.gmail.com> (raw)
In-Reply-To: <8739drj2pf.fsf@free.fr>
On 13 November 2011 22:29, Robert Jarzmik <robert.jarzmik@free.fr> wrote:
> As I'm a bit new to barebone, and after reading a bit the code for the ARM
> architectures, I have questions :
>
> ...
>
> (2) In arch/arm, I understand that interruptions are never used (do_irq()
> implementation is quite clear about that). Is that a design decision and
> why ?
> If so, I suppose that active polling for each device is required. Am I
> right here ?
>
Barebox is a firmware. So there are two main requirements for firmware:
* easy adaptation for new board (new board revision);
* small RAM/ROM footprint.
No interrupt support will help you to fulfill the both requirements.
Moreover, if you have a board with some interrupt damage (e.g. PCI
interrupt pin broken or
erroneously routed) you can start firmware and easy find the problem.
But if your firmware use the interrupts and your board have broken
PCI interrupts
and console on RS232 connected via PCI when ... you will have very
funny hardware quest :)))
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-11-14 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 18:29 Barebox newbie questions : arch/arm/{plat,mach} " Robert Jarzmik
2011-11-14 8:37 ` Sascha Hauer
2011-11-14 9:34 ` Antony Pavlov [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='CAA4bVAGvndiAjGmNGNeJGm=R_t+fm6krwqVHjhqBftBm-wP6Cg@mail.gmail.com' \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=robert.jarzmik@free.fr \
/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