So like all the whining about how circuitco and x-y-z needs to get busy doing drivers for x-y-z feature. I dont know where you guys have been for the last 6-7 months but I have yet to find much of anything that does not work with the BBB. SO the SGX/DRM drivers dont work . . .BFD this is not a computer platform but an embedded system platform.
Seems to me that some of you could apply yourselves more to get whatever it is you wish to work with the hardware. especially considering the cost of the hardware is so small. On Sun, Dec 29, 2013 at 5:29 PM, William Hermans <[email protected]> wrote: > "BTW, How are you going to add an LCD to the RPi, since you only have the > HDMI, and no LCD connector?" > > SPI ? I2C ? UART ? Pretty sure even the rPI has two of the three listed . > .. even if it does only have 16 or so GPIO's exposed. > > > On Sun, Dec 29, 2013 at 2:55 PM, Ulf Samuelsson <[email protected]>wrote: > >> 2013-12-29 20:41, Anguel skrev: >> >> >> On Monday, December 23, 2013 10:21:55 PM UTC+1, Terry Storm wrote: >>> >>> >>> A little birdy told me that Angstrom has been abandoned for the BBB ?? >>> >>> >> Terry, I will comment on this topic risking to get some angry feedback >> from other people posting here. My theory is the following: Koen Kooi was >> the one who did all Angstrom development and answered all related questions >> in groups, forums and IRC in the past (just look around). According to his >> public Google profile he is not working for CircuitCo anymore but for >> Linaro. Since then, nobody really cares about Angstrom. Angstrom server is >> down for a long time, no updates, etc. >> >> >> >> git clone https://github.com/Angstrom-distribution/setup-scripts.git >> >> git checkout -b Yocto1.5 origin/angstrom-v2013.12-yocto1.5 >> >> git log >> >> commit 0b3a4809fafebc742e7a2976ee7570a652547b71 >> Author: Koen Kooi <[email protected]><[email protected]> >> Date: Mon Dec 16 20:53:41 2013 +0100 >> >> layerman: switch OE-core to angstrom branch >> >> Signed-off-by: Koen Kooi >> <[email protected]><[email protected]> >> >> commit 55e9feb35c3a43474178e7b1be18c17e3128a611 >> Author: Koen Kooi <[email protected]><[email protected]> >> Date: Sat Dec 7 09:11:03 2013 +0100 >> >> layerman: switch meta-oe to angstrom staging branch >> >> Signed-off-by: Koen Kooi >> <[email protected]><[email protected]> >> >> commit 466ad02bec29b1499883f5d8b4540b0949cdd9d6 >> Author: Koen Kooi <[email protected]><[email protected]> >> Date: Fri Dec 6 18:57:45 2013 +0100 >> >> >> Does not sound that dead to me.... >> >> >> >> A long time ago, I had also posted some issues + bug fixes to >> meta-beagleboard but there was no reaction. >> >> Most people on #beagle IRC have no idea about Angstrom or Openembedded, >> so no community support there too. >> >> You want to post to the openembedded mailing lists. >> >> Additionally, Angstrom is a "strange" Linux distro and only a few >> people know about its details. Afaik it was Koen Kooi who chose it for the >> BBB for some reason. Another big problem that BBB development faces is the >> need to switch to device tree. >> >> >> When I build Angstrom for the Beaglebone, it is using device trees. >> >> >> Additionally, I personally don't understand why so much has been >> invested in some stupid fancy on-board development tools etc. instead of >> getting the basic things done properly. >> >> Maybe this was required by some marketing manager to be able to fool >> new developers that the BBB is very user friendly and to buy the board... >> >> Regarding the BBB kernel, afaik all the work is done by RobertCNelson who >> is also working on Ubuntu/Debian development. >> >> So what could be our options for the future of the BBB: >> 1. We can hope that Ubuntu/Debian for BBB get better and better and >> finally replace Angstrom as the official distro. >> 2. Another possibility is that TI relases a new version of their EZSDK >> with support for a new kernel, device tree, latest Qt and 3D. But according >> to the work done so far, people don't expect much from TI. >> >> TI Supports their kernel at >> git://git.yoctoproject.org/meta-ti >> which contains linux-3.12 >> >> >> 3. My hope is that the very active developers at Buildroot soon have >> good support for the BBB, so we can get access to new software packages and >> a very good embedded build system and we could finally forget Angstrom. >> >> Angstrom is based on openembedded-core and meta-openembedded, but is not >> using the standard repos. >> You need to check out the Yocto-1.5 branch to get access to the latest >> stuff though. >> If you clone the master, you do not see much development,since this is >> based on Yocto-1.3 which sees little development. >> >> Buildroot is not Yocto compliant, which means that they will not follow >> mainstream development funded by large companies. >> >> >> No matter what people tell you, BBB is very very very far from the >> Raspberry Pi's software quality and its huge community. >> CircuitCo and TI advertise the BBB wherever they can but their promises >> are far from reality. >> Why does CircuitCo still advertise their LCDs as working with latest >> Angstrom after all the discussions I had with them here in the groups? >> >> Many people here tell you that everybody should learn Linux at bare metal >> level and should be able to write his own kernel drivers to get simple >> things done. I don't agree, >> >> I think that manufacturers like TI and CircuitCo should offer you some >> working drivers and a stable basis to get started with. >> >> I agree 100%. >> >> >> We are buying their chips! Currently they don't support us. >> I have even read postings from expert developers who don't get why the >> BBB kernel is organized in the way it is, so things are very complex. >> >> I do not understand why you refer it as the BBB kernel. >> Angstrom meta-beagleboard allows you to compile the linux kernel with >> some extra patches for the am335x chips, >> using a selected kernel configuration. >> >> This is exactly what they are doing in the Buildroot project, exept that >> they do not keep track of the beaglebone >> so the number of available patches are minimal. >> >> Most embedded chip companies are focused on aligning themselves with the >> Yocto project. >> Yocto is barebone, and Angstom allows for much more advanced >> functionality. >> >> >> >> >> If you are a new developer you are just not able to learn everything, >> even if you don't do anything else in your job. IMHO this means: Only >> wealthy big companies can afford to hire dozens of developers to develop >> one product they are going to sell in masses. And if this is the only >> possibility, this is a very very bad thing for Embedded Linux. >> >> There are plenty of small companies which use Embedded Linux. >> >> >> The BBB and R Pi are wonderful boards for single developers or small >> companies who have good ideas but don't have the money and time to do >> everything from scratch. Or like me, they develop products which are needed >> by e.g. universities but are not expected to ship in large quantities. >> Unfortunately, the obstacles we currently see with the BBB and most other >> embedded boards simply prevent such good product ideas to become real >> products. Small developers and hobbyists are just wasting their time >> believing the marketing promises of big manufacturers. >> >> The BBB has better HW than the R Pi but in the meantime I ask myself - >> what is it good for if the board does not have working software and if >> nobody can help you. >> So I am seriously considering to switch to the RPi. >> >> >> There are plenty of people that can help you, but if you want to get help >> for free, then that is a different deal. >> >> BTW, How are you going to add an LCD to the RPi, since you only have the >> HDMI, and no LCD connector? >> You can't build your own board. >> If you are not happy with the Beaglebone, you can find other AM335x >> boards where the LCD support may be working. >> >> >> Regards, >> Anguel >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/WYrk-JUAkbM/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> -- >> Best Regards >> Ulf Samuelsson >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
