linux-apus-devel

hyperCOM1 and whippet fixes

[Gordon H. <go...@gh...>]

Hi, I've got a couple of fixes for APUS 2.2.10

Fixed ser_whippet.c to compile and install as a module.

Previously it would compile as a module, but would no load with
/sbin/insmod ser_whippet
it complains about unresolved symbols

Also fixed ser_hypercom1.c to compile and install as a module.

I've got three files here.

One patch file against the latest APUS-2.2.10 cvs with all the above
fixes.
A tar.gz file containing the compiled modules.
And a readme explaining how to use the modules

I could upload them to sourceforge site or send them to Michel

What should I do with them?

Be Nice. ;)

Regards,

Gordon.

Re: hyperCOM1 and whippet fixes

[Michel <dae...@st...>]

Gordon Huby wrote:

> Fixed ser_whippet.c to compile and install as a module.
> 
> Previously it would compile as a module, but would no load with
> /sbin/insmod ser_whippet
> it complains about unresolved symbols
> 
> Also fixed ser_hypercom1.c to compile and install as a module.

Excellent! Looks like things are starting to rock and roll :)


> I've got three files here.
> 
> One patch file against the latest APUS-2.2.10 cvs with all the above
> fixes.
> A tar.gz file containing the compiled modules.
> And a readme explaining how to use the modules
> 
> I could upload them to sourceforge site or send them to Michel
> 
> What should I do with them?
> 
> Be Nice. ;)

Sign up at SourceForge and apply for developer status directly to me. Believe
me, the process isn't hard *grin*


In the meantime, you could upload the patch to the Patch Manager (Put the
readme on top of it) and maybe upload the modules to the FTP incoming
directory so we can put them in contrib or something?


TIA

Michel


-- 
                        Press every key to continue.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: hyperCOM1 and whippet fixes

[Alan B. <al...@ms...>]

hi,

> Sign up at SourceForge and apply for developer status directly to me. Believe
> me, the process isn't hard *grin*

:-)
  
> In the meantime, you could upload the patch to the Patch Manager (Put the
> readme on top of it) and maybe upload the modules to the FTP incoming
> directory so we can put them in contrib or something?

to all: If you make diffs, please use the patch manager, i can then grab
these and apply them to the sources I use to make the boot kernels -
looking forward to being able to supply people the latest serial drivers
as modules 8-)

alan

Re: hyperCOM1 and whippet fixes

[Michel <da...@re...>]

Alan Buxey wrote:

> to all: If you make diffs, please use the patch manager, i can then grab
> these and apply them to the sources I use to make the boot kernels -
> looking forward to being able to supply people the latest serial drivers
> as modules 8-)

Yes Alan, I think it would be very nice if you could build the latest 2.2 CVS
(with pending patches applied as well) on a regular basis for the test module.


A few suggestions:

- Please put the files into a subdirectory which is named like the archives


For the config:

- Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems for us
  and isn't needed anyway as we're stuck with 2.2.10 ;)

- Set CONFIG_PCI and CONFIG_PCI_OLD_PROC

- You have set CONFIG_PARPORT and CONFIG_PARPORT_AMIGA, but IIRC only
  CONFIG_M68K_PRINTER works (comments?)

- CONFIG_BLK_DEV_IDEFLOPPY: Are there IDE floppies for Amigas?

- Set CONFIG_BLK_DEV_IDESCSI (at least as a module)

- Set CONFIG_BLK_DEV_BUDDHA

- Set CONFIG_FILTER and CONFIG_SYN_COOKIES

- Set CONFIG_A2091_SCSI, CONFIG_GVP11_SCSI, CONFIG_CYBERSTORM_SCSI,
  CONFIG_CYBERSTORMII_SCSI, CONFIG_BLZ2060_SCSI, CONFIG_BLZ1230_SCSI,
  CONFIG_FASTLANE_SCSI and CONFIG_OKTAGON_SCSI

- Set CONFIG_APNE

- Set CONFIG_SLIP_COMPRESSED, CONFIG_SLIP_SMART and CONFIG_SLIP_MODE_SLIP6

- Set CONFIG_FONT_SUN12x22

- Don't set CONFIG_NVRAM, but you might set CONFIG_RTC

- Set CONFIG_HFS_FS, CONFIG_MSDOS_FS, CONFIG_VFAT_FS and maybe CONFIG_ROMFS_FS

- Set CONFIG_SOUND_OSS and CONFIG_SOUND_SOFTOSS (it's a software synthesizer
  for MIDI stuff)

- Finally, set CONFIG_MAGIC_SYSRQ


I leave to you what you build into the kernel and what as modules. In general,
Stuff which isn't needed at boot time (before modules can be loaded) should be
a module so the kernel isn't bloated too much.


TIA

Michel


-- 
Men are from Earth. Women are from Earth. Deal with it.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: hyperCOM1 and whippet fixes

[Alan B. <al...@ms...>]

hi,

> Yes Alan, I think it would be very nice if you could build the latest 2.2 CVS
> (with pending patches applied as well) on a regular basis for the test module.

this I will do. 

i was thinking....now 2.3 'works', should I also make a 2.3 test kernel
for the masses to use?
 
> - Please put the files into a subdirectory which is named like the archives

..could you explain?
 
> For the config:

thanks for the .config tips - I've been collecting 'wants and needs' from
people who have booted up and found no support for their required pieces -
and you also alerted me to 3 oversights (i cant believe it, but yes, silly
things did slip through - I'll be updating the 'standard 2.2.10' as well -
especially as HFS is needed to be in the kernel for people to install
LinuxPPC 2000  - i need a LinuxPPC 2k CD to test this out the new
installer when it arrives (soon!) myself)

> - Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems for us
>   and isn't needed anyway as we're stuck with 2.2.10 ;)

:-)  btw, is there any chance of us seeing .16 ? what issues are there
with the later 2.2.11/16 yada range?
 
> - Set CONFIG_SOUND_OSS and CONFIG_SOUND_SOFTOSS (it's a software synthesizer
>   for MIDI stuff)

okay
 
> - Finally, set CONFIG_MAGIC_SYSRQ

..now that it can compile and work :-)
 
> I leave to you what you build into the kernel and what as modules. In general,
> Stuff which isn't needed at boot time (before modules can be loaded) should be
> a module so the kernel isn't bloated too much.

as a general rule, local services that are needed to get the machien to
boot and install etc i compile in. 'Exotics' and things that you use once
you are booted (sound, serial, joystick, parallel) I try to make as
modules. After all, it has been known for the device type and
rootfilesystem type to be compiled as modules...ouch!  ;-)

alan

Re: hyperCOM1 and whippet fixes

[Michel <da...@re...>]

Alan Buxey wrote:

> > Yes Alan, I think it would be very nice if you could build the latest 2.2
> > CVS (with pending patches applied as well) on a regular basis for the test
> > module.
> 
> this I will do.

Thanks a lot.


> i was thinking....now 2.3 'works', should I also make a 2.3 test kernel
> for the masses to use?

Have a go please, user feedback is always very welcome - but lots of things
still don't work. (Put a *REALLY BIG FAT* warning there ;)


> > - Please put the files into a subdirectory which is named like the
> > archives
> 
> ..could you explain?

If the archive is calles vmapus-test-[date].{tar.gz,lha}, put the files in a
directory calles vmapus-test-[date] . That way the testers don't get all the
files cluttered in one directory.


> thanks for the .config tips - I've been collecting 'wants and needs' from
> people who have booted up and found no support for their required pieces -
> and you also alerted me to 3 oversights (i cant believe it, but yes, silly
> things did slip through - I'll be updating the 'standard 2.2.10' as well -

That would be very nice, thanks.


> > - Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems
> > for us and isn't needed anyway as we're stuck with 2.2.10 ;)
> 
> :-)  btw, is there any chance of us seeing .16 ? what issues are there
> with the later 2.2.11/16 yada range?

2.2 is still based on m68k and thus: no new m68k version, no new m68k version.

Besides, I've read somewhere that performance didn't exactly improve very much
after 2.2.10 ;)


> as a general rule, local services that are needed to get the machien to
> boot and install etc i compile in. 'Exotics' and things that you use once
> you are booted (sound, serial, joystick, parallel) I try to make as
> modules.

That's a very good concept IMHO.

But I don't think that we should encourage people to use the test kernels for
installing, should we?


Michel


-- 
True programmers never die, they just branch to an odd address.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: hyperCOM1 and whippet fixes

[Michel <da...@re...>]

Michel Dänzer wrote:

> > :-)  btw, is there any chance of us seeing .16 ? what issues are there
> > with the later 2.2.11/16 yada range?
> 
> 2.2 is still based on m68k and thus: no new m68k version, no new m68k
> version.

That should of course be: no new m68k version, no new APUS version.

;)


Michel


-- 
I'm so hungry, I could almost eat health food.
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86, Team *AMIGA*, AUGS

Re: hyperCOM1 and whippet fixes

[Alan B. <al...@ms...>]

hi,

> But I don't think that we should encourage people to use the test kernels for
> installing, should we?

:-)  of course not - but I will do the same for the non-test (ie the
installer) kernel. 

alan