-!- Netsplit *.net <-> *.split quits: jonibo_ | 02:22 | |
-!- Netsplit over, joins: jonibo_ | 02:28 | |
jonibo | stekern: thanks... will give it another g o | 10:03 |
---|---|---|
jonibo | stekern: many thanks, that did the trick! | 10:07 |
stekern | ok, cool, wonder what the problem was before though | 10:13 |
jonibo | hmmm... Image Type: Unknown Architecture | 10:17 |
jonibo | has the arch type ID changed since things went upstream? | 10:17 |
jonibo | yeah, I don't know what was wrong before... it was a clean checkout from your tree which you said you could build fine | 10:18 |
jonibo | i didn't build the u-boot on the board so it may be from an older u-boot... | 10:18 |
stekern | jonibo: ah, yeah, it has changed | 10:22 |
jonibo | ok | 10:22 |
stekern | it's a bit of a pain, but it was necessary | 10:23 |
jonibo | sure, no worries, I understand | 10:23 |
stekern | since it is an increasing number | 10:23 |
jonibo | as a quick and dirty, can I change it back to the old number in my tree? | 10:23 |
jonibo | if yes, where? | 10:23 |
jonibo | ok, found it | 10:24 |
jonibo | what was it before? | 10:24 |
stekern | http://git.openrisc.net/cgit.cgi/stefan/u-boot/diff/include/image.h?id=73b553d99a9df8b2cc28c54e3473d8b2c3a115a6 | 10:24 |
jonibo | thx | 10:24 |
jonibo | 92! | 10:24 |
jonibo | surprising | 10:24 |
jonibo | i would have guessed 20 | 10:25 |
stekern | yes, don't ask, can't remember why I picked that ;) | 10:25 |
stekern | I guess I just took a large enough so I wouldn't have to change if new archs got merged before or | 10:25 |
jonibo | interesting... now I get the undefined reference to 'ethoc_initialize' error again... | 10:26 |
stekern | how are you building things? | 10:26 |
jonibo | and changing the ARCH number back to 21 resolves that...??? | 10:26 |
jonibo | CROSS_COMPILE=or32-aac-elf- make -j12 | 10:26 |
jonibo | nothing special | 10:27 |
stekern | sounds strang | 10:27 |
stekern | e | 10:27 |
jonibo | and now I set it to 92 again and this time it works | 10:27 |
jonibo | something doesn't seem to be happening in the right order | 10:28 |
jonibo | oh well... | 10:28 |
stekern | does a make distclean before you make change things? | 10:28 |
jonibo | will try | 10:28 |
jonibo | works after a distclean | 10:29 |
stekern | i usually do make distclean && make board_config, if I have changed anything in the header files | 10:29 |
jonibo | yeah, that's a good idea | 10:29 |
jonibo | but it was broken right from a clean checkout | 10:29 |
stekern | yeah, that was strange | 10:30 |
jonibo | what load address should i use? | 10:30 |
jonibo | 0, right? | 10:30 |
stekern | yes, 0 | 10:31 |
stekern | and 0x100 for execution | 10:31 |
jonibo | entry point 0x100 | 10:31 |
jonibo | right, thx | 10:31 |
stekern | yeah, the e is probably an abbrevation for entry point, not execution :P | 10:32 |
jonibo | it's almost working now, in any case | 10:32 |
jonibo | just had the ep wrong | 10:32 |
stekern | tools/mkimage -n 'Linux for OpenRISC' -A or1k -O linux -T kernel -C none -a 0 -e 0x100 -d /path/to/vmlinux.bin uImage | 10:32 |
stekern | that's the command line I'm using | 10:32 |
jonibo | cool, that's what I've got now | 10:33 |
jonibo | yay, it boots! | 10:34 |
jonibo | many thanks! | 10:34 |
jonibo | will integrate the uImage build into the kernel | 10:34 |
stekern | nice one, I've been meaning to myself, but never got around to it | 10:35 |
jonibo | what's the status of hte device tree bits | 10:35 |
stekern | they are solid :) | 10:35 |
jonibo | does u-boot handle that? | 10:35 |
jonibo | where does it find the device tree? | 10:35 |
stekern | from wherever you like | 10:35 |
jonibo | ok | 10:36 |
jonibo | i'll read up | 10:36 |
stekern | you just load it into memory before you boot linux | 10:36 |
jonibo | yup | 10:36 |
stekern | as long as there is driver support for the device to read in for it should "just work" | 10:36 |
jonibo | good good | 10:36 |
stekern | driver support in u-boot that is, but you probably got that | 10:37 |
jonibo | I saw that it's possible build the device tree right into the u-boot image, too | 10:37 |
jonibo | was thinking that might be the smartway to do it | 10:37 |
stekern | yeah, you can do that too | 10:37 |
jonibo | then again, there are disadvantages to that, too | 10:37 |
jonibo | anyway, nice work | 10:37 |
stekern | and once you have the device tree in memory, u-boot knows how to modify it, so you can do some on the fly board identification in u-boot and adjust accordingly | 10:38 |
jonibo | aha, why should u-boot do the board identification? the OS could do that itself? | 10:39 |
stekern | just as an example | 10:39 |
jonibo | u-boot should set up stuff that it knows about but that OS can't figure out for itself | 10:39 |
jonibo | like memory size, for example, if u-boot knows about that | 10:39 |
jonibo | but I understand what you're saying... | 10:39 |
stekern | yeah sure, board identification was probably a bad example | 10:40 |
jonibo | :) | 10:40 |
stekern | changin the kernel command line in the device tree on the fly is perhaps a better one | 10:41 |
jonibo | yeah, that's a relevant example ;) | 10:41 |
jonibo | (couldn't come up with any good example, myself, either) | 10:41 |
juliusb | jonibo: nice to see you're getting some time to play with OR stuff again :) | 11:58 |
jonibo | yeah, for sure, it's been a while | 12:49 |
pgavin | once I've built and run or1ksim on vmlinux, is there any way to interact with it? | 20:19 |
olofk | Interact with or1ksim? | 20:30 |
pgavin | um | 20:48 |
pgavin | yeah, like play with a shell in the simulated linux | 20:48 |
pgavin | just to make sure it's working | 20:48 |
pgavin | I mean, it looks like it works :) | 20:48 |
olofk | pgavin: Look up the uart section in the or1ksim config. You can either make it start an xterm, or connect via a socket | 21:10 |
pgavin | ok | 21:11 |
pgavin | thanks :) | 21:11 |
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!