We are not going to make a board without eMMC. Creating a bunch of different boards does not help.
If a manufacturer somewhere wants to make a board without eMMC, well, they just need to not put it on. All the design material for making this board is and always has been freely available. Anybody can build a board if they want to. All the material is open source. It is all described on the WIKI. http://www.elinux.org/Beagleboard:BeagleBoneBlack#Terms_of_Use But you cannot use the BeagleBone or BeagleBoard name. We control manufacturing. If we can't control manufacturing, it won't have the BeagleBoard name on it. Gerald On Tue, Apr 15, 2014 at 2:31 PM, rh_ <[email protected]> wrote: > On Mon, 14 Apr 2014 07:01:14 -0400 > Jason Kridner <[email protected]> wrote: > > > > > Never say never, but we are unlikely to make any more 2GB eMMC models. > > I've been kicking around the idea of doing a kickstarter for a no-eMMC > > model, but I'd like to wait a month or two to see how the Rev C and > > Element14 boards are doing out there. > > We call this a not-yes. Or not-yet-no. > > Do you know what number of boards is the sweet spot for manufacture? > I'd guess it depends on the manufacturer. > > What would be required for a manufacturer to make the BBB with no > eMMC? Are there any impediments to providing a PCB maker with > all the information and paying them to make 50 BBB? What > restrictions apply? Does the design and goal need to be annointed > or blessed to make it legal and legit? > > > > The only data we have is from the manufacturer and the community. > > After a year, we aren't seeing wear-out issues. The ext4 file system > > if fairly robust, but if writes start failing, end-user failures can > > occur in odd ways. If you are creating a mission-critical app that > > must stay deployed for many years without the ability to perform > > replacements, I'd encourage you to alter the eMMC contents to > > read-only, except for your critical data acquisition. > > There was some mention on this list that mixing read-only with > writable partitions on eMMC was potential problem since eMMC > wear-leveling don't know partitions. > > -- > 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. > -- 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.
