I have been following this discussion about the C compiler and can no
longer stop myself from making a (snarky?) comment.
The K standard for C was very much written when the C language was a
higher than assembler language for the PDP-11 (at least that's how I became
acquainted with it back in
I might be doing something wrong here, I was just responding to Adriano's
post - which I thought remained at the bottom of my response.
On 24 October 2015 at 10:00, Andrew Simmons wrote:
> I’m not sure where you’re up to, so apologies if this isn’t helpful, but
> to get the
I don't have the Plan9 uSD card handy, but to the best of my recollection
all Raspberry Pi SD cards have at least two partitions on them. The ARM
processor remains halted upon reset and the VideoCore loads the image from
the (first?) DOS formatted partition. Once that image is loaded into RAM,
Hi Brian,
Plan 9 works really well on a Raspberry Pi B for me. Haven't tried it on a
RasPi 2 yet though.
I would be rather cautious about so called compatible products. I have yet
to meet a product that is truly compatible and the quirks tend to take up a
disproportionate amount of time to
Plan9 kernel is monolithic with the drivers required for a specific
platform compiled in.
So you might need to write specific drivers for new hardware if they are
not already available.
The paper: http://plan9.bell-labs.com/wiki/plan9/compiling_kernels/ explains
the steps required to generate a
Thank you for the clarification, I was puzzling over similar issues.
You could also consider 9vx http://swtch.com/9vx/ especially if you are
tempted to try running under Qemu or some other virtualised environment.
Although I'm only at the exploratory stage, I find 9vx more useful than
9front.
I
I think that Plan9Port using the underlying Linux OS might be a better
choice. I have also been thinking about cross-compiling from a Plan9
install (such as that on Raspberry Pi) to Samsung ARM based ChromeBook.
Getting Plan9 to work with fastboot and implementing device drivers for the
various