Re: [patch] Add a dummy interrupt handler to nios2 crt0.s

Corinna Vinschen <[email protected]>
Newsgroups gmane.comp.lib.newlib
Message-ID <[email protected]>
Hi Sandra,

On Apr  2 14:01, Sandra Loosemore wrote:
> The attached patch addresses another request from the QEMU maintainers in my
> quest to get the nios2 bare-metal support patches committed there:  the
> corresponding libgloss BSP needs to provide an interrupt handler so the QEMU
> emulation can point at it.
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2019-03/msg07063.html
> 
> I added a dummy routine and placed it immediately after the 32-byte reset
> vector.  This matches where the real hardware (a 3c120 board) we've also
> used for testing expects to find the interrupt handler.
> 
> The dummy handler busy-waits in a loop, which is not terribly useful by
> itself, but you could set a breakpoint on it in the debugger, at least.
> 
> OK?

Can you please send patches in `git format-patch' format?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
Red Hat
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlykYksACgkQ9TYGna5E
T6DQiw/+It9mkXqdDaoLKQj0Vw4TBwag3mo+GZW4YEvTbiTg1fgbDS0J/VOe/Khd
2nyOvuI1yAUNLKl/gRxQaMK9oUo2ErFJ/mzw49PumnGjfdCFmcXiWPXrXZTBpnk7
dn0ZehfIcBGkbj2kB3wlldIBkptFdWFxOStbkzMAPc/nJTUo08jZwdxR+W0lppy5
mEEL2o0MFy6xp/7R3rXkzy7ZeDLQlpcg4E08tGmLEs4Hb9ZZ26QURohC8BbWDOPB
3nNfaPPDACYdAjnvMLGYqCZNvhY63U8E8+PrKm1TKqPFYDWctUOf0xFHyrXTSab6
d/aMU1PYdsGHQDTSqto0XksqC/tvZn11o4NIP+ga6TrhvlBRnjwMDmMXesh9nH8R
w7ZNN4lfWYyuvX8KkA456cNmJvwQwHWWn5B9OayO3J0XXDGST/vhmTsdoaJ2Uc5n
BY2itkyDGDNZKk2cVXxK9dG9hrklbOvN3BHKxd+icXp1re9CZ6ABajVpWOn9w030
DznV+TtTKeI6tGeGVsdMjW/+4dNZprnNmJT0BzKEZ7oXYi6G6aVCNG4DzWKYGbvk
5/b1CdXqFIHQUJAf4iwmt+jUhBOaRRiF4UmrFooTFdcAS6Fa5mfGSiYrK9TIxjBP
hAKrjpj8IAl+xfHmSQjzbzsei8M/XktitogzA92+JWTzq3gPU0I=
=7TPr
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.