[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: JFFS2 endianness.
well whatever you do. do it soon. I don't want to start going down
one path and then have to upgrade customers who will not be pleased
that we have to copy out all of the data and then reformat the disk
just to get our latest software......
Jim Gettys wrote:
> It is the best compromise, it is simple to do in advance.
> I'm not familiar with Dave's code, so won't say if it is at
> all feasible to retrofit. That is clearly Dave's call.
> - Jim
>>From: Mike Sundius <firstname.lastname@example.org>
>>Date: Thu, 17 Jan 2002 13:16:52 -0800
>>To: Jim Gettys <email@example.com>
>>Cc: David Woodhouse <firstname.lastname@example.org>,
>>Subject: Re: JFFS2 endianness.
>>Jim Gettys wrote:
>>>The other attitude is what we did in X, where the core protocol
>>>does "server makes it right", and byte swaps appropriately if needed.
>>>This isn't much of the overall code, if done well, and guarantees
>>>no overhead in the common "on machine" case. It just isn't very hard
>>>at all... :-).
>>> - Jim
>>that sounds like the best compromise. that way you can maintain
>>compatibility w/ existing filesystems.....
> Jim Gettys
> Cambridge Research Laboratory
> Compaq Computer Corporation
To unsubscribe from this list: send the line "unsubscribe jffs-dev" in
the body of a message to email@example.com