If you can stand a very slow web site:
http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G137510...
There is apparently an unofficial Fedora 19 image which boots (http://forum.odroid.com/viewtopic.php?f=62&t=2366). I've no idea if/where they are making source available, or even if it needs patches.
The hardware is interesting:
- Cortex A15, hence at least the potential of virtualization support. It's not clear if there are any firmware roadblocks to this actually working.
- 8 core big.LITTLE (ie. 4 x A15 + 4 x A7). Is there any support for this upstream yet? I read an article in LWN indicating it was rather complicated to support properly.
- A bit low on RAM (2 GB).
- A fan(!)
Any opinions on this one?
Rich.
On Sat, Oct 05, 2013 at 07:46:15AM +0100, Richard W.M. Jones wrote:
There is apparently an unofficial Fedora 19 image which boots (http://forum.odroid.com/viewtopic.php?f=62&t=2366). I've no idea if/where they are making source available, or even if it needs patches.
Source (or something) is published here: http://dn.odroid.com/ODROID-XU/
Rich.
I decided to avoid this one, and instead wait for the next Chromebook with 5420. Here is a rough list of my reasons:
This board has the Exynos 5410, an octo core big.LITTLE with virt extensions. There was a nasty rumor about 5410, evidently it had problems WRT to cluster migration (switching cores).
Samsung announced the 5420 a short while later, which was marketed as having improved benchmarks, faster clocks speed, etc. The rumor mill was speculating Samsung corrected the bugs in 5410.
Also the 5410 uses PowerVR, and the new stuff is Mali. These both suck, but arguably Mali sucks less.
Then there is the Hardkernel folks. They have somebody over there that likes Fedora, has in the past released Fedora remix. That is really cool!
I've also heard the HK folks have problems up-streaming or supporting their kernels. They were characterized as more interested in selling boards than supporting them. I've no idea if that is true or not, but I trust the (unnamed) source of this rumor.
My guess is there was a really good deal on surplus 5410 chips, really good deal! Blow out prices. ;-)
It does look like a great board though, but buyer beware!
my .02 bits
-Jon
On Sat, Oct 5, 2013 at 2:15 AM, Richard W.M. Jones rjones@redhat.com wrote:
On Sat, Oct 05, 2013 at 07:46:15AM +0100, Richard W.M. Jones wrote:
There is apparently an unofficial Fedora 19 image which boots (http://forum.odroid.com/viewtopic.php?f=62&t=2366). I've no idea if/where they are making source available, or even if it needs patches.
Source (or something) is published here: http://dn.odroid.com/ODROID-XU/
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Sat, Oct 5, 2013 at 11:45 AM, Jon jdisnard@gmail.com wrote:
I decided to avoid this one, and instead wait for the next Chromebook with 5420.
Has anyone tried to wire up serial to the current Chromebook?
Anyone heard rumors about an Arndale board with the 5420? Insignal was planning to sell an Arndale board with the 5410 [1], but I'm not sure if that's still the case.
Thanks, Arun
On Sat, Oct 05, 2013 at 01:27:43PM -0400, Arun Thomas wrote:
On Sat, Oct 5, 2013 at 11:45 AM, Jon jdisnard@gmail.com wrote:
I decided to avoid this one, and instead wait for the next Chromebook with 5420.
Has anyone tried to wire up serial to the current Chromebook?
How about a USB serial port?
Anyone heard rumors about an Arndale board with the 5420? Insignal was planning to sell an Arndale board with the 5410 [1], but I'm not sure if that's still the case.
Is the Arndale actually available to buy? Their website is still "coming soon" in November.
Rich.
On 05/10/13 18:34, Richard W.M. Jones wrote:
On Sat, Oct 05, 2013 at 01:27:43PM -0400, Arun Thomas wrote:
On Sat, Oct 5, 2013 at 11:45 AM, Jon jdisnard@gmail.com wrote:
I decided to avoid this one, and instead wait for the next Chromebook with 5420.
Has anyone tried to wire up serial to the current Chromebook?
How about a USB serial port?
Anyone heard rumors about an Arndale board with the 5420? Insignal was planning to sell an Arndale board with the 5410 [1], but I'm not sure if that's still the case.
Is the Arndale actually available to buy? Their website is still "coming soon" in November.
Rich.
http://www.arndaleboard.org/wiki/index.php/Main_Page
BUY NOW says mailto:sales@insignal.co.kr Regards Sid.
On 05/10/13 18:34, Richard W.M. Jones wrote:
On Sat, Oct 05, 2013 at 01:27:43PM -0400, Arun Thomas wrote:
On Sat, Oct 5, 2013 at 11:45 AM, Jon jdisnard@gmail.com wrote:
I decided to avoid this one, and instead wait for the next Chromebook with 5420.
Has anyone tried to wire up serial to the current Chromebook?
How about a USB serial port?
Anyone heard rumors about an Arndale board with the 5420? Insignal was planning to sell an Arndale board with the 5410 [1], but I'm not sure if that's still the case.
Is the Arndale actually available to buy? Their website is still "coming soon" in November.
Rich.
I don't see 54xx series and these are only 2 CPU's. http://www.howchip.com/shop/content.php?co_id=ArndaleBoard_en
*Arndale-5250 Package-B*
1. CPU Board - CPU : Samsung Exynos 5 Dual Cortex-A15 core 1.7 GHz - DDR3/ DDR3(L) - PMIC : S5M8767A
2. Base Board - Micro SDcard, Serial UART, USB 2.0 Device - USB 2.0 Host x 2, USB 3.0 - JTAG , Ethernet (10/100 Mbps), HDMI support - Accelerator, Gyro, e-Compass - Connector support (Sub Boards)
3. Sub Boards - Sound Board *WM1811A or Realtek ALC5631Q - Connectivity Board *MediaTek MT6620: (WiFi, BT, GPS, FM)
More detail..! http://www.howchip.com/shop/item.php?it_id=AND5250B
*Price : $249.00 USD*
Regards Sid.
W dniu 05.10.2013 19:27, Arun Thomas pisze:
On Sat, Oct 5, 2013 at 11:45 AM, Jon <jdisnard@gmail.com mailto:jdisnard@gmail.com> wrote:
I decided to avoid this one, and instead wait for the next Chromebook with 5420.Has anyone tried to wire up serial to the current Chromebook?
http://www.de7ec7ed.com/2013/05/application-processor-ap-uart-samsung.html
http://www.de7ec7ed.com/2013/05/embedded-controller-ec-uart-samsung.html
On Sat, Oct 5, 2013 at 7:46 AM, Richard W.M. Jones rjones@redhat.com wrote:
If you can stand a very slow web site:
http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G137510...
There is apparently an unofficial Fedora 19 image which boots (http://forum.odroid.com/viewtopic.php?f=62&t=2366). I've no idea if/where they are making source available, or even if it needs patches.
The hardware is interesting:
Cortex A15, hence at least the potential of virtualization support. It's not clear if there are any firmware roadblocks to this actually working.
8 core big.LITTLE (ie. 4 x A15 + 4 x A7). Is there any support for this upstream yet? I read an article in LWN indicating it was rather complicated to support properly.
A bit low on RAM (2 GB).
A fan(!)
Any opinions on this one?
I would like to support the various ODROID (and I think there's over a dozen of them) but at the moment we don't support any of the Exynos platforms well at the moment and upstream they still haven't managed to land even the basic Multi Platforms support for that kernel which pretty much kills us dead to support it well. I believe Linaro have the action item to land to MP support and I've been told since around 3.7 that it'll be "next cycle" but it never seems to make it. Once MP support lands we'll start to look at it closer.
Peter
On 06/10/13 10:06, Peter Robinson wrote:
On Sat, Oct 5, 2013 at 7:46 AM, Richard W.M. Jones rjones@redhat.com wrote:
If you can stand a very slow web site:
http://www.hardkernel.com/renewal_2011/products/prdt_info.php?g_code=G137510...
There is apparently an unofficial Fedora 19 image which boots (http://forum.odroid.com/viewtopic.php?f=62&t=2366). I've no idea if/where they are making source available, or even if it needs patches.
The hardware is interesting:
Cortex A15, hence at least the potential of virtualization support. It's not clear if there are any firmware roadblocks to this actually working.
8 core big.LITTLE (ie. 4 x A15 + 4 x A7). Is there any support for this upstream yet? I read an article in LWN indicating it was rather complicated to support properly.
A bit low on RAM (2 GB).
A fan(!)
Any opinions on this one?
I would like to support the various ODROID (and I think there's over a dozen of them) but at the moment we don't support any of the Exynos platforms well at the moment and upstream they still haven't managed to land even the basic Multi Platforms support for that kernel which pretty much kills us dead to support it well. I believe Linaro have the action item to land to MP support and I've been told since around 3.7 that it'll be "next cycle" but it never seems to make it. Once MP support lands we'll start to look at it closer.
Peter _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
I raised the question with the hardkernel kernel maintainer support some time ago about having ODROID supported in the upstream kernel so that it can keep pace with kernel development.
The answer was that it never will, citing max98090 HDMI sound and Mali400 as 2 reasons.
I tried the odroid-3.11-rc3 branch only to find out it was the upstream kernel so may be these are just placeholders for future porting to ODROID.
What I do is to clone a repository and check if there is a odroidx_defconfig. I checked the 3.11-rc7 branch, there is no odroidx_defconfig and it's not documented anywhere what will run.
The other branches, e.g 3.11-rc3 is no longer there.
The latest kernel I built and am running is 3.8.13.10. root@odroid:/usr/src/linux-3.8.13.10# uname -r 3.8.13.10 root@odroid:/usr/src/linux-3.8.13.10# cat .git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = git://github.com/hardkernel/linux.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "odroid-3.8.y"] remote = origin merge = refs/heads/odroid-3.8.y root@odroid:/usr/src/linux-3.8.13.10# git branch -a * odroid-3.8.y remotes/origin/HEAD -> origin/odroid-3.0.y remotes/origin/master remotes/origin/odroid-3.0.y remotes/origin/odroid-3.10.y remotes/origin/odroid-3.11-rc3 remotes/origin/odroid-3.11-rc4 remotes/origin/odroid-3.11-rc7 remotes/origin/odroid-3.4.y remotes/origin/odroid-3.5.y remotes/origin/odroid-3.8.y remotes/origin/odroid-3.8.y-rt remotes/origin/odroid-next remotes/origin/odroidx-3.6.y remotes/origin/odroidxu-3.4.y
Regards Sid.
On Sun, Oct 06, 2013 at 10:06:59AM +0100, Peter Robinson wrote:
I would like to support the various ODROID (and I think there's over a dozen of them) but at the moment we don't support any of the Exynos platforms well at the moment and upstream they still haven't managed to land even the basic Multi Platforms support for that kernel which pretty much kills us dead to support it well. I believe Linaro have the action item to land to MP support and I've been told since around 3.7 that it'll be "next cycle" but it never seems to make it. Once MP support lands we'll start to look at it closer.
Sorry to ask what may be obvious, but "Multi Platforms support" means device tree support?
Rich.
On Sat, Dec 7, 2013 at 3:30 PM, Richard W.M. Jones rjones@redhat.com wrote:
On Sun, Oct 06, 2013 at 10:06:59AM +0100, Peter Robinson wrote:
I would like to support the various ODROID (and I think there's over a dozen of them) but at the moment we don't support any of the Exynos platforms well at the moment and upstream they still haven't managed to land even the basic Multi Platforms support for that kernel which pretty much kills us dead to support it well. I believe Linaro have the action item to land to MP support and I've been told since around 3.7 that it'll be "next cycle" but it never seems to make it. Once MP support lands we'll start to look at it closer.
Sorry to ask what may be obvious, but "Multi Platforms support" means device tree support?
No, it means booting a single kernel on multiple SoCs. Basically going back to prior to 3.7 we had to have a different kernel for each SoC (tegra/imx/highbank/omap/versatile) and now we have a single kernel for pretty much everything. DT tends to be one of the things that come with that but it's not necessary or dependent.
Peter
On Sat, Dec 07, 2013 at 03:52:12PM +0000, Peter Robinson wrote:
On Sat, Dec 7, 2013 at 3:30 PM, Richard W.M. Jones rjones@redhat.com wrote:
On Sun, Oct 06, 2013 at 10:06:59AM +0100, Peter Robinson wrote:
I would like to support the various ODROID (and I think there's over a dozen of them) but at the moment we don't support any of the Exynos platforms well at the moment and upstream they still haven't managed to land even the basic Multi Platforms support for that kernel which pretty much kills us dead to support it well. I believe Linaro have the action item to land to MP support and I've been told since around 3.7 that it'll be "next cycle" but it never seems to make it. Once MP support lands we'll start to look at it closer.
Sorry to ask what may be obvious, but "Multi Platforms support" means device tree support?
No, it means booting a single kernel on multiple SoCs. Basically going back to prior to 3.7 we had to have a different kernel for each SoC (tegra/imx/highbank/omap/versatile) and now we have a single kernel for pretty much everything. DT tends to be one of the things that come with that but it's not necessary or dependent.
OK, device tree describes the layout of the hardware. What other sorts of differences between SoCs need to be considered? (I thought that ARM instruction sets were compatible within ARM versions?)
The reason for asking all this is I'm trying to understand what's going on with the hardkernel ODROID-XU Linux tree.
Rich.
No, it means booting a single kernel on multiple SoCs. Basically going back to prior to 3.7 we had to have a different kernel for each SoC (tegra/imx/highbank/omap/versatile) and now we have a single kernel for pretty much everything. DT tends to be one of the things that come with that but it's not necessary or dependent.
OK, device tree describes the layout of the hardware. What other sorts of differences between SoCs need to be considered? (I thought that ARM instruction sets were compatible within ARM versions?)
Mostly. There's some differences as some devices don't have NEON (like SSE), and A8, A9 etc evolve with newer instructions but then that's no different to x86 either but generally yes.
The reason for asking all this is I'm trying to understand what's going on with the hardkernel ODROID-XU Linux tree.
Primarily it's implementation. The various SoCs would basically (I don't know the full and exact details) implement certain calls differently on the various SOCs so that depending on how you compile the kernel it can change, the "unified" multi platform kernel is about cleaning that all up and essentially being able to identify the different implementations at runtime similar to how the x86 detects Intel vs AMD vs Via implementations.
Peter
-
Arun Thomas -
Jon -
Marcin Juszkiewicz -
Peter Robinson -
Richard W.M. Jones -
Sid Boyce