| --- Log opened Mon Jan 20 00:00:02 2014 | ||
| maxpaln | _franck_web_ & LoneTech: to let you know - I found the caue of the issue! Thanks for your time on Friday - it was to do with the memory blocks inferred by Synplify. Ethernet interface working now! :-) | 10:49 |
|---|---|---|
| olofk_ | maxpaln: Good to hear | 10:52 |
| olofk_ | _franck_: I've thought a bit about having a next branch for orpsoc. I'm not really sure, but that's maybe because I'm not that good at git. | 10:54 |
| olofk_ | My idea now is that the git master is unstable, and that I should do proper releases often enough to let people get the new features | 10:54 |
| jonibo | by "unstable", do you mean you commit 'crap' to it? that's the wrong approach... | 11:04 |
| jonibo | if you mean "unstable" as in "not released yet", that's fine | 11:05 |
| jonibo | you don't really need releases if master is kept "working"... -next branch is good for giving people a chance to test master before it _really_ becomes master, but if nobody tests it then its pointless... that said, -next isn't for 'crap'/'work in progress' either, that's what topic branches are for | 11:06 |
| jonibo | my two cents worth | 11:06 |
| olofk_ | jonibo: Sounds reasonable | 11:18 |
| olofk_ | So given that there are very few users right now, commits to the master branch is somewhat tested and that most of the new stuff that comes in are new features, a next branch might not get much use | 11:20 |
| olofk_ | No fancy new OpenRISC features in 3.13 according to kernelnewbies | 11:34 |
| olofk_ | stekern: Is the VGA/LCD driver targeted for 3.14? | 11:34 |
| olofk_ | jonibo: Is everything from your tree merged into upstream? | 11:37 |
| _franck_ | maxpaln: great ! | 11:40 |
| maxpaln | with that conundrum solved I want to mount a file system on the SPI Flash so everything isn't erased with each boot. | 11:56 |
| maxpaln | in the kernel I've enabled UBI (under MTD support) and UBIFS (under the Miscellaneous File Systems config) | 11:57 |
| maxpaln | but the kernel doesn't include any of the binaries for creating and managing a UBIFS | 11:57 |
| maxpaln | is this expected/a known limitation of the openrisc kernel? | 11:57 |
| jonibo | olofk_: no, my tree is the "mess" that works with the rest of the ecosystem... uClibc, et al.... some of that is never going upstream but is targeted to be removed from my tree when the rest of the ecosystem allows | 12:01 |
| jonibo | the for-upstream branch is the stuff that's targeted at upstream | 12:02 |
| jonibo | ...and gets pulled into linux-next | 12:02 |
| jonibo | maxpain: userspace binaries for managing ubifs are part of mtd-utils project... they are not part of the kernel | 12:04 |
| jonibo | I think you can get some of the functionality from busybox, too... but it's limited | 12:05 |
| maxpaln | ok, well jffs2 might be an easier way to prove the concept then return to it later once higher priority things are working! | 12:06 |
| maxpaln | thanks though | 12:06 |
| -!- marguerite is now known as Guest55875 | 17:03 | |
| stekern | olofk_: yes, it's queued up for 3.14 | 19:36 |
| stekern | and for the record, I've successfully used ubifs with busybox | 19:37 |
| stekern | and off the record, I'm in salzburg and have just enjoyed some very nice locally brewed weissbier ;) | 19:41 |
| --- Log closed Tue Jan 21 00:00:03 2014 | ||
Generated by irclog2html.py 2.15.2 by Marius Gedminas - find it at mg.pov.lt!