From: prem <prem.mallappa@gmail.com>
To: 9fans@9fans.net
Subject: [9fans] ARMv6 compiler ? (was: more bitsy stuff)
Date: Mon, 17 Mar 2008 09:50:02 +0000 [thread overview]
Message-ID: <ff79a6fb-a1d9-4fe5-9bee-6cd0be518ad5@s12g2000prg.googlegroups.com> (raw)
In-Reply-To: <9ec71d3874fdd404d8cb37689c588d2f@csplan9.rit.edu>
Hi All,
I am thinking of porting Plan9 to latest ARM cores including v6 and v7
(in my upcoming holidays). I think the compiler is old (pre-v5) though
i am not sure.
could anyone tell me if 5c and friends support v6. if it doesn't how
difficult it is to add it?
Also I have installed latest inferno sources from google svn (on
Linux). is it possible to (cross-)compile plan9 sources on Linux ?
thanks
/Prem
On Mar 14, 2:20 am, j...@csplan9.rit.edu wrote:
> So it turns out that I can build a kernel that will boot Axel's old
> paqdisk without a problem, but if I use my own kernel with my own
> freshly created paqdisk, I get the crash below:
>
> root is from (paq)[paq]:
>
> paq...paqfs: sysfatal reading block: /dev/flash/ramdisk:
>
> version...panic: boot process died: sys: write on closed pipe pc=0x00006c74
>
> panic: boktrace /kernel/path c0010d28 c011714c c01171a9
>
> ot procc01170f8=c0010d24 ess diec01170fc=c0070aec d: sys:c0117104=c003afe4 write c0117128=c003b044 on clos
>
> ed pipe c0117140=c003b2a8 pc=0x00c0117144=c0010d24 006c74
> c0117148=c003b2ac
> c0117150=c006d790
>
> c01171b0=c008d610 c01171b4=c008d3bc c01171bc=c008f200 c01171c8=c0078f94
>
> c01171d4=c008d14c c01171d8=c008e37c c01171dc=c008d510 c01171e0=c008d14c
>
> c01171e8=c008d3f8 c01171f4=c008d3bc c01171fc=c008f200 c0117208=c0078f94
>
> c011721c=c008f6c0 c011723c=c006022c c0117248=c006add0 c0117250=c006add8
>
> c011725c=c006d750 c0117274=c00108f8 c0117280=c00790b8 c0117284=c0079594
>
> c01172ac=c0070fc0 c01172b4=c00108dc c01172c8=c0010418 c01172e8=c0008248
>
> c01172f0=c0079594
>
> it's a wonderful day to die
>
> This makes me think that there was perhaps a change in mkpaqfs along
> the line? To look at the error, it seems that there's something wrong
> with my ramdisk image; any insights, anyone? Who has been maintaining
> the bitsy stuff?
>
> John
next prev parent reply other threads:[~2008-03-17 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 21:14 [9fans] more bitsy stuff john
2008-03-17 9:50 ` prem [this message]
2008-03-17 12:39 ` [9fans] ARMv6 compiler ? (was: more bitsy stuff) Charles Forsyth
2008-03-17 17:55 ` [9fans] ARM compiler erik quanstrom
2008-03-17 21:46 ` Richard Miller
2008-03-17 22:28 ` Rob Pike
2008-03-18 4:16 ` Bruce Ellis
2008-03-18 5:07 ` erik quanstrom
2008-03-18 6:10 ` Bruce Ellis
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=ff79a6fb-a1d9-4fe5-9bee-6cd0be518ad5@s12g2000prg.googlegroups.com \
--to=prem.mallappa@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).