| --- Log opened Thu Apr 02 00:00:48 2015 | ||
| olofk | Is anyone interested in keeping the or1200 option for the systems in FuseSoC? I'm inclined to remove them starting with de0_nano. | 06:06 |
|---|---|---|
| olofk | For de0 nano I'm also looking at throwing out a lot of the other `ifdefs as well and let people copies of the system if they want less SPI and I2C controllers | 06:08 |
| bandvig | olofk: I'm not interested in or1200 | 07:26 |
| olofk | bandvig: I'm not interested in or1200 either, and I think most people are fine with mor1kx | 08:10 |
| olofk | bandvig: And regarding your question about the uart version, it's a bit tricky. I've been trying to find time to implement some proper versioning support, but I'm not there yet. | 08:11 |
| olofk | I did a proper release (1.5) of uart16550 just for that reason, to have a known good version | 08:11 |
| olofk | Hmm.. could u-boot be set to use the wrong IRQ for UART perhaps? | 10:56 |
| _franck__ | olofk: u-boot doesn't use IRQ | 11:46 |
| Hesham | Yeah | 11:46 |
| Hesham | Is there anyway to force terminating qemu from the running or1k apps? like with l.nop 0xc on or1ksim? | 11:47 |
| poke53281 | https://github.com/qemu/qemu/blob/master/target-openrisc/translate.c#L749 | 11:55 |
| poke53281 | @Hesham: According to this line, there is no special behavior for l.nop | 11:55 |
| Hesham | poke53281: Thanks. I may add a patch because it's useful to terminate qemu from the apps. | 12:00 |
| Hesham | I added a patch to terminate QEMU if l.nop received 0xc as an argument. It'll be used part of RTEMS Tester, let me know if I should submit it. | 14:39 |
| poke53281 | Is 0xc also used in or1ksim? | 15:17 |
| Hesham | poke53281: Yeah | 15:19 |
| poke53281 | Then I think, you can try to submit it. | 15:20 |
| Me1234 | Look here: https://github.com/openrisc/linux/blob/master/drivers/net/phy/micrel.c#L16 | 17:49 |
| Me1234 | Looks like that ksz8051 is not supported. | 17:49 |
| Me1234 | No, actually it is supported https://github.com/openrisc/linux/blob/master/drivers/net/phy/micrel.c#L635 | 17:50 |
| Me1234 | May this https://github.com/torvalds/linux/commit/2b0ba96cea6066d2543066fa524120b384f3bd6b commit fix the kernel panic I have with ethernet ? | 18:29 |
| olofk | Me1234: Hmm... maybe, but you should also check your pin configuration on the board. Depending on how you set them, the phy will start up in nand-tree or MII mode | 19:05 |
| olofk | But looking at the schematics for your board, it should be in MII mode if all the CONFIG0-2 jumpers are removed | 19:12 |
| Me1234 | olofk: The error happens is here: https://github.com/torvalds/linux/blob/master/drivers/net/phy/micrel.c#L564 | 19:24 |
| Me1234 | olofk: I think it is an error in DTS. | 19:24 |
| Me1234 | What should the PHY address be? 0 or 1? | 19:30 |
| --- Log closed Fri Apr 03 00:00:49 2015 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!