[haiku-development] Re: Haiku over Raspberry PI

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 10 Jul 2017 09:07:39 -0500

On 2017-07-10 09:01, kallisti5 wrote:

On 2017-07-10 08:51, Rahul Jain wrote:
Small side note on this stuff, i'm working on redoing the arm architecture
port over here:

https://github.com/kallisti5/haiku/tree/arm-noboards

Going full fdt with no per-board targets.

I'd avoid changing anything around the "board_config.h" or anything with a
ifdef around board type.


I am not so good at it , But this may conflict in terms of loading on
other arm boards .. Right ?

No.  So historically we had a bunch of headers with hardcoded addresses
of various devices for various boards for the kernel + loader.

mmu_man, myself, and others began implementing fdt in our bootloader
and kernel which are compiled files describing the hardware the code
is being run on.

Just found a good example of the changes in one of my commits:
https://github.com/kallisti5/haiku/commit/1e82d7bd254f26623d713bfb9008f076d5ea3c0d#diff-fd24b67edd884e21d9a1c98da545b855L98

The BOARD_* defines came from various known boards specified via
--target-board to configure. We can do away with all the hard-coded addresses
and use fdt to explore what hardware is available:

https://github.com/haiku/haiku/blob/b65adbdfbc322bb7d86d74049389c688e9962f15/src/system/kernel/platform/u-boot/fdt_serial.cpp#L44


 -- Alex

Other related posts: