http://www.beagleboard.org/about

On Wednesday, June 18, 2014 7:53:49 PM UTC-5, William Hermans wrote:
>
> Hi Scott,
>
> Thanks for clarifying. I guess I found the whole write-up at LinuxGizmos 
> rather confusing. Part of the problem on my behalf is that I guess I've 
> viewed Circuitco, and beagleboard.org as kind of the same entity. The 
> other part of my confusion is that the write-up seems to be all over the 
> place.
>
>
> On Wed, Jun 18, 2014 at 5:30 PM, Bill Traynor <[email protected] 
> <javascript:>> wrote:
>
>> On Wed, Jun 18, 2014 at 1:19 AM, William Hermans <[email protected] 
>> <javascript:>> wrote:
>> > From what I could gather from the article, these are embest ./ element14
>> > boards. Kind of hard to read through as one part of the article seems 
>> like
>> > it's implying one thing, where in another it seems to go another 
>> direction.
>> >
>> >
>>
>> The board is produced by CircuitCo.  It's a great little board with
>> just the right stuff removed to make it more palatable for some.  I
>> like it a lot.
>>
>> > On Tue, Jun 17, 2014 at 10:16 PM, John Syn <[email protected] 
>> <javascript:>> wrote:
>> >>
>> >>
>> >> From: William Hermans <[email protected] <javascript:>>
>> >> Reply-To: "[email protected] <javascript:>" <
>> [email protected] <javascript:>>
>> >> Date: Tuesday, June 17, 2014 at 9:17 PM
>> >> To: "[email protected] <javascript:>" <
>> [email protected] <javascript:>>
>> >> Subject: Re: [beagleboard] BeagleBoard SBC Goes OEM, COM Version Coming
>> >>
>> >> Funny how these articles always seem to report stuff that's either
>> >> incorrect or not entirely accurate.
>> >>
>> >> I think the overlying information given by the site is nice to know ( 
>> such
>> >> as new hardware being released ), but their actual write-ups are 
>> nothing
>> >> more than FUD. The article you linked to had several points of
>> >> misinformation, such as the BBB's processor speed ( but somehow they 
>> managed
>> >> to get it right in the table of board differences ).
>> >>
>> >> Anyway, the board sound interesting, but personally I think they went 
>> the
>> >> wrong direction in removing the eMMC. and am pretty sure it can be 
>> disabled
>> >> via device tree overlays if additional IO's are needed ( which really 
>> wont
>> >> give you many back anyway.).HDMI on the other hand, I'd never miss.
>> >>
>> >> Looks like the same board as the BBB with the eMMC and HDMI chips not
>> >> populated. I’m sure Gerald & circuitco have analyzed the market 
>> requirement
>> >> and this is what the market wants. If you have the numbers, I’m sure 
>> they
>> >> will manufacture a batch with the eMMC populated or you could always 
>> add it
>> >> yourself.
>> >>
>> >>
>> >>
>> >> Don't even get me started with "Angstrom is prefered by most / more
>> >> professional developers . . ." Because that is plain B.S.  Also the
>> >> statement "Moving to the more user friendly Debian
>> >>  . . ." Is fairly hilarious. Mainly because many long time users of 
>> other
>> >> distro's seem to have a hard time grasping the concepts of a more
>> >> traditional Linux distro like Debian. For the record though this 
>> statement
>> >> is accurate as Debian actually has real / proper documentation. Where
>> >> Angstrom falls flat on its face
>> >>
>> >> I could go on, and on, but the fact is that "real professionals" are 
>> going
>> >> to use what makes the most sense for their project. If they want small,
>> >> Angstrom is probably the last thing in their minds. QNX, or Busybox on 
>> a
>> >> microkernel come to mind far ahead of anything else.
>> >>
>> >>
>> >> On Tue, Jun 17, 2014 at 6:44 PM, John Syn <[email protected] 
>> <javascript:>> wrote:
>> >>>
>> >>>
>> >>> 
>> http://www.linux.com/news/embedded-mobile/mobile-linux/777154-beaglebone-sbc-goes-oem-com-version-coming
>> >>>
>> >>> Interesting how we are the last to know about this!
>> >>>
>> >>> Regards,
>> >>>
>> >>> John
>> >>>
>> >>>
>> >>> --
>> >>> 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] <javascript:>.
>> >>> For more options, visit https://groups.google.com/d/optout.
>> >>
>> >>
>> >> --
>> >> 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] <javascript:>.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >>
>> >> --
>> >> 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] <javascript:>.
>> >> For more options, visit https://groups.google.com/d/optout.
>> >
>> >
>> > --
>> > 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] <javascript:>.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/d/optout.

Reply via email to