Menu
▾
▴
linux-apus-devel
|
From: Ken T. <ke...@we...> - 2001-05-17 16:19:16
|
On Thu, 17 May 2001, Geert Uytterhoeven wrote: > On Fri, 18 May 2001, Ken Tyler wrote: > > Has not compiled since 2.2 AFAIK, unless it was fixed in m68k and the > > changes didn't make it to APUS. > > I remember mailing them to Vojtech, and they even made it to Linus, IIRC. > Of course this doesn't prevent anybody from breaking the stuff again later... amijoy.c:66: unterminated macro call amijoy.c:161: unterminated macro call amijoy.c: In function `amijoy_interrupt': amijoy.c:66: parse error before `;' amijoy.c:68: parse error before `;' amijoy.c: In function `amijoy_open': amijoy.c:79: `IRQ_AMIGA_VERTB' undeclared (first use in this function) amijoy.c:79: (Each undeclared identifier is reported only once amijoy.c:79: for each function it appears in.) amijoy.c:81: `amijoy_irq' undeclared (first use in this function) amijoy.c: In function `amijoy_close': amijoy.c:93: `IRQ_AMIGA_VERTB' undeclared (first use in this function) amijoy.c: In function `amijoy_setup': amijoy.c:100: syntax error before `str' amijoy.c:101: `ints' undeclared (first use in this function) amijoy.c: In function `amijoy_init': amijoy.c:108: syntax error before `)' amijoy.c:47: warning: `amijoy_used' defined but not used amijoy.c:50: warning: `amijoy_name' defined but not used amijoy.c:73: warning: `amijoy_open' defined but not used amijoy.c:89: warning: `amijoy_close' defined but not used amijoy.c:107: warning: `amijoy_init' defined but not used Could of course be finger trouble here. Ken. |
|
From: Michel <mic...@ii...> - 2001-05-17 16:45:49
|
Ken Tyler wrote: >=20 > On Thu, 17 May 2001, Geert Uytterhoeven wrote: >=20 >=20 >>On Fri, 18 May 2001, Ken Tyler wrote: >> >=20 >>>Has not compiled since 2.2 AFAIK, unless it was fixed in m68k and the >>>changes didn't make it to APUS. >>> >>I remember mailing them to Vojtech, and they even made it to Linus, IIR= C. >>Of course this doesn't prevent anybody from breaking the stuff again la= ter... >=20 > amijoy.c:66: unterminated macro call > amijoy.c:161: unterminated macro call > amijoy.c: In function `amijoy_interrupt': > amijoy.c:66: parse error before `;' > amijoy.c:68: parse error before `;' > amijoy.c: In function `amijoy_open': > amijoy.c:79: `IRQ_AMIGA_VERTB' undeclared (first use in this function) > amijoy.c:79: (Each undeclared identifier is reported only once > amijoy.c:79: for each function it appears in.) > amijoy.c:81: `amijoy_irq' undeclared (first use in this function) > amijoy.c: In function `amijoy_close': > amijoy.c:93: `IRQ_AMIGA_VERTB' undeclared (first use in this function) > amijoy.c: In function `amijoy_setup': > amijoy.c:100: syntax error before `str' > amijoy.c:101: `ints' undeclared (first use in this function) > amijoy.c: In function `amijoy_init': > amijoy.c:108: syntax error before `)' > amijoy.c:47: warning: `amijoy_used' defined but not used > amijoy.c:50: warning: `amijoy_name' defined but not used > amijoy.c:73: warning: `amijoy_open' defined but not used > amijoy.c:89: warning: `amijoy_close' defined but not used > amijoy.c:107: warning: `amijoy_init' defined but not used >=20 > Could of course be finger trouble here. Nope, I get the same. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Michel <mic...@ii...> - 2001-05-17 11:32:02
|
Alan Buxey wrote: >>>Do we need Minix fs support yet? >>> >>Not for installation. >=20 > the ramdisk image no longer uses MiniFS? if so minifs could be dropped > ages ago. You mean our test ramdisk.image.gz ? I asked eons ago if we should conver= t it=20 to ext2, if it's still Minix we should do that now. We could use it as a=20 rescue or other fancy stuff with a current glibc etc. > I guess we also dont need OCS gfx support...as PowerPC cards only work = on > ECS and AGA systems. > =20 > On this line of thought...sound isnt essential, neither is parallel por= t?, > joystick.. I already considered all this and am now at 848 K. How much space exactly= do=20 we have? --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Geert U. <ge...@li...> - 2001-05-17 11:45:43
|
On Thu, 17 May 2001, Michel D=E4nzer wrote:
> I already considered all this and am now at 848 K. How much space exact=
ly do=20
> we have?
IIRC you have 837 kB free on an OFS-formatted floppy. Since we all use FF=
S
these days it (at least the kernel) should fit. And don't use DC-FFS sinc=
e it
will waste^H^H^H^H^Hconsume even more diskspace.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org
In personal conversations with technical people, I call myself a hacker. =
But
when I'm talking to journalists I just say "programmer" or something like=
that.
-- Linus Torvalds
|
|
From: Michel <mic...@ii...> - 2001-05-17 12:28:52
|
Geert Uytterhoeven wrote: > > On Thu, 17 May 2001, Michel Dänzer wrote: > > I already considered all this and am now at 848 K. How much space exactly > > do we have? > > IIRC you have 837 kB free on an OFS-formatted floppy. Since we all use FFS > these days it (at least the kernel) should fit. And don't use DC-FFS since > it will waste^H^H^H^H^Hconsume even more diskspace. :) AFAIR FFS gives the full 880K minus a few? BTW if we could use bzip2, we'd be all set already: michdaen@pismo> du -sk vmapus.bz2 ~/src/apus-cvs/2.4 776 vmapus.bz2 -- Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \ XFree86 and DRI project member |
|
From: Geert U. <ge...@li...> - 2001-05-17 12:43:34
|
On Thu, 17 May 2001, Michel D=E4nzer wrote:
> Geert Uytterhoeven wrote:
> > On Thu, 17 May 2001, Michel D=E4nzer wrote:
> > > I already considered all this and am now at 848 K. How much space e=
xactly
> > > do we have?
> >=20
> > IIRC you have 837 kB free on an OFS-formatted floppy. Since we all us=
e FFS
> > these days it (at least the kernel) should fit. And don't use DC-FFS =
since
> > it will waste^H^H^H^H^Hconsume even more diskspace.
>=20
> :) AFAIR FFS gives the full 880K minus a few?
>=20
> BTW if we could use bzip2, we'd be all set already:
>=20
> michdaen@pismo> du -sk vmapus.bz2 ~/src/apus-=
cvs/2.4
> 776 vmapus.bz2
Has no one added bzip2 support to zlib yet?
However, the increased size of zlib may offset the decreased size of the
kernel.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6=
8k.org
In personal conversations with technical people, I call myself a hacker. =
But
when I'm talking to journalists I just say "programmer" or something like=
that.
-- Linus Torvalds
|
|
From: Alan B. <al...@ms...> - 2001-05-17 13:12:24
|
hi, > BTW if we could use bzip2, we'd be all set already: this is a weakness of 'bootstrap', yes? alan |
|
From: Alan B. <al...@ms...> - 2001-05-17 13:34:00
|
hi,
> You mean our test ramdisk.image.gz ? I asked eons ago if we should convert it
> to ext2, if it's still Minix we should do that now. We could use it as a
> rescue or other fancy stuff with a current glibc etc.
yep, dropping minix will cleave a small lump off the kernel.
> I already considered all this and am now at 848 K. How much space exactly do
> we have?
well, if we need the following
s:startup-sequence - a few bytes...
libs:ppc.library (for powerup - not needed for A1200, but for a3k/a4k
a1200 has this in ROM)
*or* we go with WarpUP....which ever has the smallest libraries
envarc: a few bytes of required env: variables for WarpUP (if used)
the boot tool (eg one i'm working on.....) tens of K
could be compressed (eg with stonecracker) if
needed)
bootstrap + the bootstrap_pup or bootstrap_wup - 100's of k's
How much fits onto one 880K formatted disk, i cant recall, its been so
long....is it 856k?
I can see the kernel needing to be ~500k ....nasty....could 2.2.10 get
this small?
alan
|
|
From: Michel <mic...@ii...> - 2001-05-17 15:23:15
|
Alan Buxey wrote: > > I already considered all this and am now at 848 K. How much space exactly > > do we have? > > well, if we need the following > > s:startup-sequence - a few bytes... > libs:ppc.library (for powerup - not needed for A1200, but for a3k/a4k > a1200 has this in ROM) > *or* we go with WarpUP....which ever has the smallest libraries > envarc: a few bytes of required env: variables for WarpUP (if used) > the boot tool (eg one i'm working on.....) tens of K > could be compressed (eg with stonecracker) if > needed) > bootstrap + the bootstrap_pup or bootstrap_wup - 100's of k's > > How much fits onto one 880K formatted disk, i cant recall, its been so > long....is it 856k? > > I can see the kernel needing to be ~500k ....nasty....could 2.2.10 get > this small? I doubt it. Brainstorming: We could throw out _all_ disk drivers except that for the floppy; everything else would have to be loaded as modules. This brings it down to 660K. OTOH the modules will take lots of space; is there some kind of limit, e.g. from the ramdisk size? We could make one floppy with just the kernel on it and another one which boots, copies everything to RAM: and... you get the idea. -- Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer CS student, Free Software enthusiast \ XFree86 and DRI project member |
|
From: Alan B. <al...@ms...> - 2001-05-17 13:44:24
|
hi, > We could make one floppy with just the kernel on it and another one which > boots, copies everything to RAM: and... you get the idea. yes, that may have to be the way.... disk1:bootstrap -k disk2:vmlinux.gz type-stuff alan |
|
From: Duncan G. <DG...@Du...> - 2001-05-17 18:23:59
|
On 17-May-01, Alan Buxey wrote: AB> How much fits onto one 880K formatted disk, i cant recall, AB> its been so long....is it 856k? I think it depends which filesystem you use, and whether you have many small files verses few big ones. For a disk mostly filled with one large file (like a kernel image), FFS should be more efficient, since it doesn't put headers on every block, IIRC, using all 512 bytes for actual data. FFS has been in ROM since v37, so it should be safe to assume everyone can boot from an FFS disk. Except maybe a (very) few A3000 users. If you get really desperate, there exist crunchers which can store Amiga (68K) executables in a cruched format and decompress them as they load. Don't know if anyone's used these under an at all recent version of AmigaOS, though. Duncan -- ... You sound reasonable...Time to up my medication. |
|
From: Sven L. <lu...@dp...> - 2001-05-17 10:35:00
|
On Wed, May 16, 2001 at 09:28:01PM +0200, Geert Uytterhoeven wrote: > On Wed, 16 May 2001, Michel D=E4nzer wrote: > > Sven LUTHER wrote: > > > > I am trying to understand why... > > > > For an 880k floppy the space problem makes impossible to do it. > > > > But i wish to be contraddicted... :)) > > >=20 > > > Well, we could split the kernel in 2 and join it in ram: before lau= nching > > > it. Or we could try for a less than 880Ko modular kernel, but i hav= e not big > > > hopes on this one. > >=20 > > I am experimenting, and it looks promising. I basically moved everyth= ing > > except video and disk drivers to modules and here's what it gives so = far: > >=20 > > michdaen@pismo> gzip -cv9 vmlinux > vmapus.gz ~/src/apu= s-cvs/2.4 > > vmlinux: 60.1% > > michdaen@pismo> ll vmapus.gz ~/src/apu= s-cvs/2.4 > > -rw-r--r-- 1 michdaen src 888321 May 16 19:49 vmapus.gz > > michdaen@pismo> du -k vmapus.gz ~/src/apu= s-cvs/2.4 > > 868 vmapus.gz > >=20 > > Is this small enough? I guess I could squeeze out a few more K... >=20 > Probably not yet. >=20 > > Do we need support for foreign partition maps? >=20 > Not for installation. >=20 > > Do the fbcon packed pixels modules work? >=20 > Yes, but only for modular drivers. >=20 > I'd say include fbcon-afb (amifb), fbcon-cfb8 (gfx cards) and fbcon-cfb= 16 > (gfx cards with amiboot -v). >=20 > You don't need fbcon-ilbm since amifb doesn't need it unless you use > video=3Damifb:ilbm. >=20 > You don't need fbcon-mfb since amifb will fallback to fbcon-afb/fbcon-i= lbm for > depth 1 when fbcon-mfb is not available. >=20 > You don't need fbcon-cfb24 and fbcon-cf32 since no one wants to run an = install > console in those depths anyway. I don't think you need it for half-supp= orted > gfx cards with amiboot -v, only depth 16. Also do you have pm2fb and co in there ? maybe this 880 ko kernels would = be only for aga, this way we have only 1 possible video=3D mode in the amibo= ot script. Other modes can be choosen later on. Friendly, Sven Luther |
|
From: Sven L. <lu...@dp...> - 2001-05-17 10:33:01
|
On Wed, May 16, 2001 at 07:58:06PM +0200, Michel D=E4nzer wrote: > Sven LUTHER wrote: >=20 > > > I am trying to understand why... > > > For an 880k floppy the space problem makes impossible to do it. > > > But i wish to be contraddicted... :)) > >=20 > > Well, we could split the kernel in 2 and join it in ram: before launc= hing > > it. Or we could try for a less than 880Ko modular kernel, but i have = not big > > hopes on this one. >=20 > I am experimenting, and it looks promising. I basically moved everythin= g > except video and disk drivers to modules and here's what it gives so fa= r: >=20 > michdaen@pismo> gzip -cv9 vmlinux > vmapus.gz ~/src/apus-= cvs/2.4 > vmlinux: 60.1% > michdaen@pismo> ll vmapus.gz ~/src/apus-= cvs/2.4 > -rw-r--r-- 1 michdaen src 888321 May 16 19:49 vmapus.gz > michdaen@pismo> du -k vmapus.gz ~/src/apus-= cvs/2.4 > 868 vmapus.gz mmm, a bit just maybe, will it fit with amiboot and the script ? But, we definitively need 2 batches of kernels, since i suppose some guys would want the networking stuff also. They can use the non floppy version though. > Is this small enough? I guess I could squeeze out a few more K... >=20 > Do we need support for foreign partition maps? not really, they could be modules. > Do the fbcon packed pixels modules work? >=20 > Do we need Minix fs support yet? Not anymore, since now root images are ext2 fs, not minix, but i am not s= ure, please someone confirm this. > The other side of the story will probably be the space needed for the > modules... That's no problem, the infrastructure is there already for splitten modules.tgz file, they come in 3 floppies for i386. i guess the module re= ading and joining is size independent, we just would need to add the stuff to c= ut it in 880 or 720 Ko chunks (but i386 already support 1.44, 1.2 and 2.88 ones= , so the stuff is in there already). Friendly, Sven Luther |
|
From: Michel <mic...@ii...> - 2001-05-17 11:37:46
|
Sven LUTHER wrote: > But, we definitively need 2 batches of kernels, since i suppose some gu= ys > would want the networking stuff also. They can use the non floppy versi= on > though. Can't they use the modules? I'd really like to have a single .config,=20 otherwise maintenance is a nightmare. >>Is this small enough? I guess I could squeeze out a few more K... >> >>Do we need support for foreign partition maps? >=20 > not really, they could be modules. No they can't. I've removed anything but Amiga, I think those who really = need=20 something else should build their own kernels. > Also do you have pm2fb and co in there ? maybe this 880 ko kernels woul= d be only for aga, this way we have only 1 possible video=3D mode in the amibo= ot script. Other modes can be choosen later on. I don't think this is feasible as some people won't have anything connect= ed to their AGA output. Right now all the Amiga framebuffer devices are in. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Alan B. <al...@ms...> - 2001-05-17 13:33:29
|
hi, > I don't think this is feasible as some people won't have anything connected > to their AGA output. Right now all the Amiga framebuffer devices are in. agreed - a lot of people either dont have a monitor that can 'do' the AGA modes (even the 29.xHz VGA thing) , others dont have scan-doublers or TV's handy (if they've got a modulator). recovering/installing etc is bad enough..without having to unplug/digaround etc for a display device... of course, if it were my choice I'd say ditch all gfx and we'll go for serial-output - after all, everyone should have a vt100 terminal 8-) alan |
|
From: Geert U. <ge...@li...> - 2001-05-17 13:38:44
|
On Thu, 17 May 2001, Alan Buxey wrote:
> > I don't think this is feasible as some people won't have anything connected
> > to their AGA output. Right now all the Amiga framebuffer devices are in.
>
> agreed - a lot of people either dont have a monitor that can 'do' the AGA
> modes (even the 29.xHz VGA thing) , others dont have scan-doublers or TV's
> handy (if they've got a modulator).
Note that `vga' and `vga70' in Linux/amifb are real 31 kHz modes, not the
`approximating' stuff from AmigaOS.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Sven L. <lu...@dp...> - 2001-05-14 12:19:48
Attachments:
rescue.sh.diff
|
On Fri, May 11, 2001 at 10:38:07PM +0200, Giorgio Terzi wrote:
> Hello Sven,
>
> In first i wish to thank you for your help and for your last
> e-mail. :)))
>
> But let's speak about job.
>
> The second goal is reached!
>
> Now is possible to load & install Rescue & Driver images from
> floppies, CD-ROMS,HD-Partitions.
> But to do this we must correct some bugs :
>
> Bug 1: dbootstrap
>
> The APUS rescue image is MSDOS formatted but in file
> choose_medium.c from line 34 the code is so:
> #if cpu(sparc) || #cpu(powerpc)
> const char *fs_type_tab[] = { "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
> as you can understand is impossible for a powerpc machine
> to load a msdos partition, so i have modified it so:
> #if cpu(sparc) || #cpu(powerpc)
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
I changed this to :
#if cpu(sparc)
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
Should work, i think. Does one of the powerpc boot floppies people have
anything to say about it before i commit ?
> After this, rescue.bin was loaded and kernel extracted & configured.
> I think this #if is obsolete because, as you will see some lines
> after in the source file , mount loops between the various filesystems
> (msdos & ext2 now, but may will be more ?) attempting
> to load the image files.
>
> For CD-ROM & for HD partition loading system the drivers was also
> successfully loaded & configured.
> For CD-ROM i used my Potato CD-ROM N.1.For hard disk i have
> built a debian tree in an Amiga partition.
>
> Bug 2: floppy images build & configuration
>
> After the kernel configuration, it was renamed as vmlinuz-2.2.19,
> and this comes from the install.sh script.
> For APUS this name is wrong as it is really a 2.2.10 kernel.
> Maybe it is possible to use the $subarch variable to distinguish the
> various powerpc kernel architecture's versions during the install.sh
> configuration ?
mmm, you can use the apuskver variable defined at line 30 of the config file :
ifeq "$(architecture)" "powerpc"
kver := 2.2.19
pcmcia_kver := 2.2.19-pmac
apuskver := 2.2.10
endif
So i guess what is used is kver, not apuskver.
Notice that the install.sh script is generated at line 12 of the rescue.sh
script, from the install.sh.txt file, but passing only the kver and arch
variables, not the subarch and apuskver one. There may be need for more
extensive modification here, i don't know m4 enough to really help out here.
Also it seems to me the write_powerpc routine only knows about quick, don't
think this will be working on apus, we may be more near what the
write_m68kinfo does, ity would need testing though.
lines 396-401 of rescue.sh should be generating the right thing for apus,
altough i don't really see a reason why we shall not go the ext2 way.
It would be also be interresting to see if we need lines 450+ of rescue.sh,
about broken loop device, this sound like the loop bug of the original boot
floppies.
Line 552 of rescue.sh also has some $kver related things we shall look into.
mmm, line 573 of rescue.sh calls write_m86kinfo, so we don't have to worry
about quick as feared above, we still would need to make sure that subarch and
apuskver is passed to m4 when generating install.sh.
That's all i see in rescue.sh.
mmm, maybe this would be enough (try the attached patch) ?
write_installsh () {
if [ "x$noinstall" = x ]; then
if [ "$subarch" != apus ]; then
m4 -D__ERROR_MESS__=$scripts/messages/$language/install.sh.txt \
-D__version__=$kver -D__arch__=$arch \
<$scripts/install.sh >$mnt/install.sh
chmod 755 $mnt/install.sh
else
m4 -D__ERROR_MESS__=$scripts/messages/$language/install.sh.txt \
-D__version__=$apuskver -D__arch__=$arch \
<$scripts/install.sh >$mnt/install.sh
chmod 755 $mnt/install.sh
fi
fi
Could you try it out ?
> I have tested also the floppy disk use:
>
> Bug 3: fd0 device problems
>
> For APUS /dev/fd0 is unable to load the rescue floppy disk.
> I think it defaults to the Amiga floppy formats.
> I must erase it and recreate it with 'mknod fd0 b 2 28'
> that is the same of /dev/fd0u1440 in a "standard" installation.
>
> After this change the rescue floppy was successfully loaded.
Ok, but like said most amiga have only the 720/880Ko floppy variety.
> Bug 4: dboostrap problem.
>
> dbootsrap was not able to recognize the driver's floppy disk
> because the drivers' default names was treated as complete
> names but they are really "root names" for example:
> drv14 is a "root name"
> drv14apus.bin is a driver's complete name.
> In file floppy_merge.c i have modified the line 197 :
>
> if (!strcmp (basenames[i], block.header.name))
> as follows:
> if (!strncmp (basenames[i], block.header.name,strlen(basenames[i])))
>
> after this i have also loaded the drivers!
Ok, i read this was already by stephen Marenka, but maybe not as you say here.
I didn't found any mention to it in the cvs log file, but then i may have
missed it.
Friendly,
Sven Luther
|
|
From: Alan B. <al...@ms...> - 2001-05-15 09:19:54
|
hi,
> > #if cpu(sparc) || #cpu(powerpc)
> > const char *fs_type_tab[] = { "ext2", NULL };
> > #else
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #endif
> > as you can understand is impossible for a powerpc machine
> > to load a msdos partition, so i have modified it so:
> > #if cpu(sparc) || #cpu(powerpc)
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #else
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #endif
>
> I changed this to :
>
> #if cpu(sparc)
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
surely,
#if cpu(sparc)
const char *fs_type_tab[] = { "ext2", NULL };
#else
const char *fs_type_tab[] = { "msdos", "ext2", NULL };
#endif
this would give the powerpc the msdos and ext2, but keep the sparc - which
orginally didnt have the msdos option - as it was.
> Ok, but like said most amiga have only the 720/880Ko floppy variety.
most A4k's have a 1.76Mb internal, a lot of A1200 people have an external
HD floppy, but internal was 880k - not possible to have some choose option
(df0, df1 or skip?)
alan
|
|
From: Sven L. <lu...@dp...> - 2001-05-15 09:34:05
|
On Tue, May 15, 2001 at 10:19:33AM +0100, Alan Buxey wrote:
> hi,
>
> > > #if cpu(sparc) || #cpu(powerpc)
> > > const char *fs_type_tab[] = { "ext2", NULL };
> > > #else
> > > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > > #endif
> > > as you can understand is impossible for a powerpc machine
> > > to load a msdos partition, so i have modified it so:
> > > #if cpu(sparc) || #cpu(powerpc)
> > > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > > #else
> > > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > > #endif
> >
> > I changed this to :
> >
> > #if cpu(sparc)
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #else
> > const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> > #endif
>
> surely,
>
> #if cpu(sparc)
> const char *fs_type_tab[] = { "ext2", NULL };
> #else
> const char *fs_type_tab[] = { "msdos", "ext2", NULL };
> #endif
>
> this would give the powerpc the msdos and ext2, but keep the sparc - which
> orginally didnt have the msdos option - as it was.
Yes, that is what i meant, ...
> > Ok, but like said most amiga have only the 720/880Ko floppy variety.
>
> most A4k's have a 1.76Mb internal, a lot of A1200 people have an external
> HD floppy, but internal was 880k - not possible to have some choose option
> (df0, df1 or skip?)
Can you boot from an external 1.76MB floppy ?
also i am not sure if it would worth it to try to support 880kb floppies, as
that would mean splitting the disks over various files,
but 1.76MB floppies would be easily supported, almost nothing needs to be
changed, apart from the rescue disk creation. Does someone with a 1.76MB
floppy volunteer for that ?
Also, is there a way (under linux) to detect if the floppy is of the 1.76 or
the 880 variety ?
Friendly,
Sven Luther
|
|
From: Alan B. <al...@ms...> - 2001-05-15 10:57:41
|
hi, > Can you boot from an external 1.76MB floppy ? yes. its treated just as the old classic external floppies that I'm sure most people had with their A500's > but 1.76MB floppies would be easily supported, almost nothing needs to be > changed, apart from the rescue disk creation. Does someone with a 1.76MB > floppy volunteer for that ? if you give me the instructions and details I can test this. > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or > the 880 variety ? dont know - I always believe that floppies are too dumb..you only know what you can do when things you try fail ;-) alan |
|
From: Geert U. <ge...@li...> - 2001-05-15 11:39:53
|
On Tue, 15 May 2001, Alan Buxey wrote:
> > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or
> > the 880 variety ?
>
> dont know - I always believe that floppies are too dumb..you only know
> what you can do when things you try fail ;-)
grep FD_HD_3 linux/drivers/block/amiflop.c.
But I don't think you can easily find out from userspace.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
|
|
From: Sven L. <lu...@dp...> - 2001-05-15 12:57:44
|
On Tue, May 15, 2001 at 01:36:19PM +0200, Geert Uytterhoeven wrote: > On Tue, 15 May 2001, Alan Buxey wrote: > > > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or > > > the 880 variety ? > > > > dont know - I always believe that floppies are too dumb..you only know > > what you can do when things you try fail ;-) > > grep FD_HD_3 linux/drivers/block/amiflop.c. > > But I don't think you can easily find out from userspace. Maybe we could provide this kind of info trough the proc filesystem ? (As usual, i think your answer would be : sure you can, any volunteer ?, isn't it ?) Friendly, Sven Luther |
|
From: Sven L. <lu...@dp...> - 2001-05-15 12:43:31
|
On Tue, May 15, 2001 at 11:57:11AM +0100, Alan Buxey wrote: > hi, > > > Can you boot from an external 1.76MB floppy ? > > yes. its treated just as the old classic external floppies that I'm sure > most people had with their A500's > > > but 1.76MB floppies would be easily supported, almost nothing needs to be > > changed, apart from the rescue disk creation. Does someone with a 1.76MB > > floppy volunteer for that ? > > if you give me the instructions and details I can test this. Well, just format a floppy disk, but the bootstrap program on it, a linux kernel (in compressed form) and a little script that will boot it, from a ramdisk. Maybe the script could ask a few question before booting or something such, don't know, what would be best to ask ? You could the follwoing settings : 1first question : From where to boot ? a) from the floppy provided kernel and root image (root=/dev/mem or whatever) b) from a user provided partition c) into amigados, so the user can play himself. Don't know if the floppy would be able to contain the needed thing to provide a working amiga shell or workbench though. 2nd question : provide additional parameters. a) video option : aga, pm2fb, other, ... b) other needed options (don't know about them, ...) c) anything else ... or maybe only one question, which response would provide all of the above, like having a a') and b') above, but where the user can provide a more complete and general kernel options line. What do you think about it ? > > Also, is there a way (under linux) to detect if the floppy is of the 1.76 or > > the 880 variety ? > > dont know - I always believe that floppies are too dumb..you only know > what you can do when things you try fail ;-) What about trying to read past the 880 Kb with dd or something such ? Friendly, Sven Luther |
|
From: Christian T. S. <ct...@de...> - 2001-05-15 13:20:55
|
On Tue, May 15, 2001 at 02:45:28PM +0200, Sven LUTHER wrote: > On Tue, May 15, 2001 at 11:57:11AM +0100, Alan Buxey wrote: > > hi, > > > > > Can you boot from an external 1.76MB floppy ? > > > > yes. its treated just as the old classic external floppies that I'm sure > > most people had with their A500's > > > > > but 1.76MB floppies would be easily supported, almost nothing needs to be > > > changed, apart from the rescue disk creation. Does someone with a 1.76MB > > > floppy volunteer for that ? > > > > if you give me the instructions and details I can test this. > > Well, just format a floppy disk, but the bootstrap program on it, a linux > kernel (in compressed form) and a little script that will boot it, from a > ramdisk. Don't you need some part of AmigaOS to make a floppy bootable? Doesn't at least amiboot need some libraries to be present on the system you are booting from? Can all hardware already be set up by the kernel? How do you get the image on the floppy, from linux? From AmigaOS? It probably has to be done on an amiga to use the 1.76MB drives (or on a PC with a catweasel controller, even less probable). So I guess you need an Amgia, running AmigaOS, to create these floppies, to then be able to boot from those floppies. Probably we will not be allowed to ship those floppies or even images of them, due to copyright reasons, so every user has to create them himself. Due you really think this is worth it, considering how unreliable floppies are? Please tell me when I am too pessimistic ;-) No, I don't have a HD floppy drive, only with the catweasel controller, and no driver for it exists yet. And no, I will not put a new harddisk into my old Amiga, even if I had to set up a system from scratch, I could very well use a bootable MOD, but maybe more users have HD drives than MOs... Christian -- http://people.debian.org/~cts/ |
|
From: Sven L. <lu...@dp...> - 2001-05-15 13:31:48
|
On Tue, May 15, 2001 at 08:20:48AM -0500, Christian T. Steigies wrote: > On Tue, May 15, 2001 at 02:45:28PM +0200, Sven LUTHER wrote: > > On Tue, May 15, 2001 at 11:57:11AM +0100, Alan Buxey wrote: > > > hi, > > > > > > > Can you boot from an external 1.76MB floppy ? > > > > > > yes. its treated just as the old classic external floppies that I'm sure > > > most people had with their A500's > > > > > > > but 1.76MB floppies would be easily supported, almost nothing needs to be > > > > changed, apart from the rescue disk creation. Does someone with a 1.76MB > > > > floppy volunteer for that ? > > > > > > if you give me the instructions and details I can test this. > > > > Well, just format a floppy disk, but the bootstrap program on it, a linux > > kernel (in compressed form) and a little script that will boot it, from a > > ramdisk. > Don't you need some part of AmigaOS to make a floppy bootable? no, you just have to make it bootable with install, i think. > Doesn't at least amiboot need some libraries to be present on the system you > are booting from? mmm, yes, i think at least the powerup libraries, which reside on the powerup boards, at least in their blizzard edition. There may be some others, but i am sure you can fit them in the 1.76-1.44 = 320Ko you have left after you put the kernel there. (and geert spoke of less than 500ko m68k modular kernels). And remember those days when you didn't had harddisks on your amiga. > Can all hardware already be set up by the kernel? Sure, i guess at least most of it could. Maybe for some of the graphic cards this is not the case, but people in this case just could boot from the harddisk anyway. > How do you get the image on the floppy, from linux? From AmigaOS? It > probably has to be done on an amiga to use the 1.76MB drives (or on a PC > with a catweasel controller, even less probable). Well, you just make a 1.76MB tarball, that can be unzipped/copied on the floppy disk by the user. Also i guess with an amiga hardware, the floppy is accesible under linux, so you could dd it to it. At least this is the case with my 880Ko floppy. > So I guess you need an Amgia, running AmigaOS, to create these floppies, to > then be able to boot from those floppies. Probably we will not be allowed to No, you just need an amiga running amigaos or linux. > ship those floppies or even images of them, due to copyright reasons, so > every user has to create them himself. No, don't think so, not sure though. Amiboot/apusboot is GPled (i think, but anyway, we already ship it in the boot-floppies package) as is the kernel. The little script would be just anything you want it to be, i guess you could GPL it also. Sure you would not have GUI or workbench or ... but it would work. > Due you really think this is worth it, considering how unreliable floppies > are? Please tell me when I am too pessimistic ;-) It is easy to do (i think, will have to test though). I don't think a lot of people will use it, but it could come in handy in some cases, i guess. What do you do actually, you just copy all needed stuff to your harddisk and work from there. In the case of not having a amiga partition, you just boot into a workbench boot floppy, copy the kernel and amiboot to ramdisk, and launch it from there. > No, I don't have a HD floppy drive, only with the catweasel controller, and > no driver for it exists yet. Yes, i have it also not. It is worth a try though, don't you think, especially if people with it volunteer to do it. > And no, I will not put a new harddisk into my old Amiga, even if I had to set > up a system from scratch, I could very well use a bootable MOD, but maybe > more users have HD drives than MOs... ;))) Friendly, Sven Luther |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X