Date: Fri, 30 Jun 2006 11:50:10 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: embedded@FreeBSD.org Cc: Aditya Godbole <aag.lists@gmail.com> Subject: Re: New architecture support (fwd) Message-ID: <20060630114807.S3964@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
Since embedded is both driving (and reliant on) new architecture support, does it make sense to create some documentation on what hardware ports involve? I mean both "from scratch" and "incremental". If someone has notes, I'm sure we could get some help in converting it into a developer's handbook chapter or article. Since new hardware ports for FreeBSD appear to be done with moderate frequency, the knowledge is definitely out there. Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Fri, 30 Jun 2006 12:07:56 +0530 From: Aditya Godbole <aag.lists@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: New architecture support On 6/27/06, John Baldwin <jhb@freebsd.org> wrote: > > If I have to add support for a new architecture, how do I start? > > Well, you'll need a toolchain. :) Then you can start working on building > a minimal kernel filling in missing bits in sys/<arch> as you go. Is there any documentation regarding the interface between the machine independant and machine dependant parts of the kernel. Also what functionality does the machine independant part expect to be in place? -aditya _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060630114807.S3964>