From: Tom Rix <tom@bumblecow.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3: proposal: dont piggy back on ROMCode interrupt vectors
Date: Tue, 13 Oct 2009 07:27:29 -0500 [thread overview]
Message-ID: <4AD47231.5060908@bumblecow.com> (raw)
In-Reply-To: <4AD45800.8010008@gmail.com>
Nishanth Menon wrote:
> Hi,
> Current interrupt vectors[1] are piggy backing on OMAP3 ROM Code vectors
> This has the disadvantage that "external boot" option of OMAP GP devices
> for booting off NOR devices would probably not function as the interrupt
> vectors are not setup.
>
In general we want to limit dependencies of ROM code.
And it should be moved to omap3 so other cortexa8 users don't have to
code around it. Like we did for the cache flushing.
> I had faced this during the port of u-boot-v2 and had done an
> implementation[2] for this. would we be interested in pulling this back
> in for u-boot-v1? I suppose all OMAP3 devices could benefit from it.
>
Poking around it does not look like any of the omap boards define
CONFIG_USE_IRQ so it seems like you really will be creating the
interrupt handlers. I think this is a good idea as long as the existing
non-interrupts still works. I would be happy to test whatever you want
to do. Should we set up a special ti-omap-irq topic branch ?
Tom
> Regards,
> Nishanth Menon
>
> Ref:
> [1]
> http://git.denx.de/?p=u-boot/u-boot-ti.git;a=blob;f=cpu/arm_cortexa8/start.S;h=14a9bd3b039143f92aed2133493aa9ee6a175738;hb=HEAD#l112
> [2]
> http://git.denx.de/?p=u-boot/u-boot-v2.git;a=blob;f=arch/arm/mach-omap/omap3_core.S;h=dece199faefb3354189347d17cb0709d0ce2ad6c;hb=HEAD#l71
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
next prev parent reply other threads:[~2009-10-13 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 10:35 [U-Boot] OMAP3: proposal: dont piggy back on ROMCode interrupt vectors Nishanth Menon
2009-10-13 12:27 ` Tom Rix [this message]
2009-10-13 14:01 ` Nishanth Menon
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=4AD47231.5060908@bumblecow.com \
--to=tom@bumblecow.com \
--cc=u-boot@lists.denx.de \
/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