On Wednesday 11 June 2008, Bert Freudenberg wrote:
It's currently using the X11 display, but there is also an SDL
backend.
Would be interesting to see on fbdev ...
While the XO actually has plenty of RAM, we're currently wasting a ton
of it. I'm glad to see experiments for
On Wednesday 09 March 2011 17:31:24 Kevin Gordon wrote:
go, no-go, spend the extra pennies and get a Class 4/6/8/10
Note that Class 8 does not exist (except fakes) and class 10 is
usually not faster than class 6 if you run ext3 on it.
Also, a Sandisk card is usually faster than a card from
most
On Friday 11 March 2011, John Watlington wrote:
On Mar 9, 2011, at 2:23 PM, Arnd Bergmann wrote:
On Wednesday 09 March 2011 17:31:24 Kevin Gordon wrote:
go, no-go, spend the extra pennies and get a Class 4/6/8/10
Note that Class 8 does not exist (except fakes) and class 10 is
usually
On Friday 11 March 2011 18:28:49 John Watlington wrote:
On Mar 11, 2011, at 5:35 AM, Arnd Bergmann wrote:
I've tested around a dozen media from them, and while you are true
that they use rather different algorithms and NAND chips inside, all
of them can write to at least 5 erase blocks
On Sunday 13 March 2011 02:01:22 C. Scott Ananian wrote:
On Sat, Mar 12, 2011 at 5:51 PM, Arnd Bergmann a...@arndb.de wrote:
I've had four cards with a Sandisk label that had unusual characteristics
and manufacturer/OEM IDs that refer to other companies, three Samsung (SM)
and one unknown
On Sunday 13 March 2011, Mikus Grinbergs wrote:
The tests have also helped expose other issues with things like sudden
power off. In one case a SPO during a write would corrupt the card so
badly it became useless. You could only recover them via a super secret
tool from the
On Sunday 13 March 2011, Richard A. Smith wrote:
On 03/13/2011 01:21 PM, Arnd Bergmann wrote:
There's a 2nd round of test(s) that runs during the manufacturing and
burn-in phases. One is a simple firmware test to see if you can talk the
card at all and then one runs at burn in. It doesn't
On Monday 14 March 2011 19:50:27 John Watlington wrote:
Cards that are in the state you describe are most likely dead due to
running out of spare blocks. There is nothing that can be done to
rehabilitate them, even using the manufacturer's secret code.
In a disturbing trend, most of the
On Tuesday 15 March 2011 01:29:19 John Watlington wrote:
On Mar 14, 2011, at 3:18 PM, Arnd Bergmann wrote:
Another effect is that the page size has increased by a factor of 8,
from 2 or 4 KB to 16 or 32 KB. Writing data that as smaller than
a page is more likely to get you into the worst
On Thursday 24 March 2011 20:26:05 Christoph Derndorfer wrote:
Hi all,
the folks from the Austrian pilot project want to equip the XO-1s there with
SD cards. Are there any restrictions wrt size, speed, etc. that they should
be aware of when purchasing the SD cards? I'm particularly asking
On Friday 25 March 2011 01:27:47 Rodolfo D. Arce S. wrote:
You should try different types and brands, as long as they all have
the same size, cause, in this cases, size does matter. This way if
there is statistics that proves one brand not working is minimal
compared to the whole batch of a
On Thursday 31 March 2011 08:45:24 Yioryos Asprobounitis wrote:
I was wondering if it makes any sense when making an ext fs on an SDcard
to try to align the erase block of the card with the ext2 group size.
eg assuming a card with a 4KB pages and 4MB erase blocks, try something
like
On Thursday 31 March 2011, Yioryos Asprobounitis wrote:
--- On Thu, 3/31/11, Arnd Bergmann a...@arndb.de wrote:
From: Arnd Bergmann a...@arndb.de
The Kingston card probably uses a toshiba controller (oemid 0x544d)
[snip]
The transcend cards I've seen typically use samsung
On Saturday 02 April 2011, Yioryos Asprobounitis wrote:
Thanks for the info.
I got a new Transcend 4GB class 10 card: oemid 0x4142(AB???), manfid
0x1e(RS???), hwrev 0x1, fwrev 0x0, serial 0x0aec
and I checked it with flashbench when formatted as vfat (factory)
standard ext3
On Thursday 14 April 2011, John Gilmore wrote:
(Of course, when doing these writes, don't do one-block writes to the
drive; accumulate a bunch of them into a single larger write. If you
know the erase block size, the code could seek to do writes of that
size, aligned on that boundary -
On Thursday 14 April 2011, Daniel Drake wrote:
Hi Arnd,
As you've obviously been working with a large range of SD cards, I
wonder if you have any comments/knowledge on erase behaviour.
The SD card spec says that CMD32/CMD33 erase can leave the data as
either all-zero or all-one, depending
On Saturday 15 August 2015 21:05:48 Adam Holt wrote:
What filesystem would people recommend for ~128GB SD cards inserted into XO
laptops or XSCE servers heading far afield, to insert very large
(evolving?) digital libraries just like Internet-in-a-Box?
Multiyear reliability for all this
On Monday 21 March 2016 11:13:41 Adam Holt wrote:
> Not our first choice, but the reason we are forced to consider this hack
> (despite our distaste for sleeves/converters that sometimes fail) is that
> full-size SD's are increasingly harder to procure -- as these are no
> longer mass-market
18 matches
Mail list logo
