> I searched the archives and noted that the problem I am currently
> experiencing was reported quite some time ago with an older release -- is
> it STILL an issue, or am I merely invoking it incorrectly?
The 2.0.39 aha1542 driver still doesn't support parameters when loaded as
a module. It isn't really an open issue, it is a 'the way it is'. You
can either (1) replace the kernel with your own kernel, or (2) wait until
I get tomsrtbt upgraded to (probably) 2.2.19. Module command line ability
was added to the aha1542 driver on July 19th, 1999 <rant>IF PEOPLE WOULD
DO THEIR OWN RESEARCH AND LOOK AT THE SOURCE CODE THEMSELVES...</rant> by
Chris Faulhaber, in the 2.2.x tree only.
> Was the problem resolved? Is this an issue with the driver, or the insmod
> (should I look to pull down a _real_ insmod to try)?
The 'real' insmod was what was in tomsrtbt, when it previously occurred.
> Input would be most welcome. By convention, I don't run the 1542 at 0x300
> or 0x330 because of conflicts with other hardware. 0x234 is where they're at.
Use 334. 334 is probed by the driver <IDREF=previous rant>.
-Tom
