I'll assume you mean Angstrom and Debian. Which just a factiod for those who do not know already. Angstrom is pretty much already based on Debian. Technically Debian -> Open Zaurus -> Angstrom is the "fork path".
Moving to Debian personally makes total sense to me. Granted I've been using Debian since the 90's and am very familiar with it. However, on the same hand when I speak of Debian on this hardware do realize that I am also a newb when it comes to embedded Linux. Before I got our BBB's here ( 2 ) I had zero hands on with Linux in this capacity, and had never done any Linux development period. I see this USB babble error mentioned on the groups and have no idea where it comes from and have never experienced it. I have experienced zero problems with USB except that with 3.8.x USB hot plugging will cause a fatal crash. Knowing this, I just do not hot plug USB and there are not problems . . . and it is not as though I do not have as much experience with this board as the next person, because I was working on netbooting, USB booting, this board back in June this year ( when the board was first released to the general public ). Knowing what I do now, I would not call myself an expert, but I have learned quite a bit in the last 6-7 months. For me personally, I would never dream of using Angstrom on this fine hardware. As the second week after playing with the board I've had Debian running on it in just about every conceivable way SD card, TFTP/NFS netboot, USB, etc. Has everything worked perfectly from the start ? Hell no, I had to work at it. I took 2 weeks studying the uEnv.txt file alone. Got every bit of information I could find on the web on my own to help me understand uboot, and how it all worked. Then by the time I understood things well enough to ask a sensible question ( at least i hope it was sensible ), I asked my question, and got pointed to the C header file for uboot configuration/initialization I guess it was. Anyway, the point being is if *you* want something to work on this platform, you had better work on it yourself. Otherwise, if it does not work already you're going to be stuck getting no where. That and people like me will not care if something does not work for *you* especially considering you're not even willing to take the time to learn Linux, or even attempt to do sometime about it yourselves. I suppose a perfect example on this list would be all the conversation about QT not compiling on the BBB . . . I find the topic hilarious on multiple levels. Suffice it to say if you do not already understand why, do not bother asking . . . On Mon, Dec 30, 2013 at 3:21 PM, Gerald Coley <[email protected]>wrote: > In order to support the $45 price tag, it was a bear bones > offering. Circuitco was paying for the Angstrom support but > the maintainer left Circuitco and went to another company. > > TI supports mainline Linux, currently 3.12 and higher. We are moving in > that direction as fast as we can from the 3.3 Kernel. > > Angstrom and Linux are distributions of the Linux OS. > > Gerald > > > On Mon, Dec 30, 2013 at 4:08 PM, dave <[email protected]> wrote: > >> Allow me to add my support (AKA 2 cents) to this thread. Noting elsewhere >> that CircuitCo has shipped over 100,000 units to date, if the cost had >> included a couple of dollars for software development, that money could >> have been put to good use. Also adding to the comment on TI, if they don't >> provide support leading to the demand for the chip, the product will die. >> It is in the interest of both TI and CircuitCo to see that at least one >> underlying OS gets supported and will be around for a while. (At this point >> I don't really care if it's Debian, Ubuntu, Fedora, or even Slackware!) >> >> On my part, I just want an embedded system with Linux that "Just Runs!" I >> place myself at a level slightly higher than novice since I have used (PC >> based) Linux in previous projects. Admittedly, this platform is new and >> there will be some pain in getting there, but I don't like seeing comments >> of the nature that XXX OS is/will no longer be supported. I want to see >> support from both TI and CircuitCo to ensure the continuing support of >> their product. I just want to know that my efforts are not headed for the >> proverbial drain even before I get it running. >> >> >> On Monday, December 30, 2013 4:37:10 PM UTC-5, Mike Bremford wrote: >> >>> Aha, well that certainly explains it. Yes, I'd chip in to get cape >>> support added to one of Robert's more recent (3.12 or 3.13) kernels with >>> stable USB. Myself, I'd also be willing to pay slightly more per board >>> (reasonable, as the result would be a better product), but I realise that's >>> more contentious. >>> >>> >>> On 30 December 2013 20:52, Gerald Coley <[email protected]> wrote: >>> >>>> Circuitco, breaks even, barely. Beagleboard.org makes no money at all. >>>> >>>> TI, well they make a little of the chips, but provides no funding for >>>> BeagleBoard.org. >>>> >>>> Anyone willing to donate some funds so we can fund some SW developers? >>>> >>>> Gerald >>>> >>>> >>> -- >> 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. > -- 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.
