[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#67888: marked as done ([CVS-fixed] Netwinder/arm port shouldn't ask about maintaining 2.0 compatability)



Wookey <wookey@aleph1.co.uk> writes:

> On Tue 21 Nov, Debian Bug Tracking System wrote:
> 
> > >From andersen@codepoet.org Sat Jul 29 01:11:08 2000
> > Return-path: <andersen@codepoet.org>
> 
> > The debian installer for potato worked just fine on the netwinder, one I
> > convinced it to tftp boot the provided netwinder-rescue image.  One hitch
> > though -- the question about maintaining 2.0 compatability for the ext2 fs
> > should be removed and forced to "yes".  Answering "no" causes the
> > netwinder's firmware (which is just a stripped down linux kernel) to be
> > unable to read the filesystem -- so it is unable to boot the system.  Not
> > that big a deal though.

Could you file this as a bug?

> > >From adam@onshore.com Tue Nov 21 05:21:28 2000
> 
> > This bug was fixed in one of the last two versions of the
> > boot-floppies, either 2.2.17 or 2.2.18, both of which are in Potato
> > now.
> 
> Erm, this is all fine for netwinders, but for a riscpc (the other main arm
> desktop platform) this option does not need to be forced to yes. This is just
> one of many things that vary between arm platforms (which are fairly
> hetrogenous). I don't know what the disadvantage is, but if it affects disk
> speed then as the riscps is 'very slow' in this dept it would be nice to have
> the choice.
> 
> There are several things that need to be done differently for different arm
> sub-platforms. Is there an approved mechanism for this at the moment or not?

You'd have to ask the ARM porters.  Other arches with subarches (such
as sparc) look in /proc/cpuinfo and such and automatically deal with
this.

-- 
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>



Reply to: