[ale] Modem identification and connecting

[Alex Carver]

Well, I can't change the IrDA ports but I think the modem can be moved.
 The problem is I don't know how to tell the pcmcia/serial_cs modules to
assign the modem to another IO and IRQ.

Right now the on-board serial is 0x03f8.  The IrDA ports want to be on
0x02f8 and 0x02e8.  The modem is always assigned to 0x02f8 by serial_cs.
 If I could move that to 0x03e8 then I should be able to eliminate the
IO collisions.  And that's the problem, how do I tell pcmcia/serial_cs
to assign that device 0x03e8 when it is inserted?

On 11/10/2013 12:07, Jim Kinney wrote:
> Well, crud. A programmable serial interface would be perfect but it sounds
> like the hardware combo doesn't support it.
> On Nov 10, 2013 2:24 PM, "Alex Carver" <agcarver+ale at acarver.net> wrote:
> 
>> I'll do my best but given that this has apparently been an ongoing
>> problem since 2007 across multiple distros it seems that no one has
>> quite figured out how to resolve it.  It appears I can have IrDA -or-
>> serial but not both in some systems.  In this case some digging suggests
>> an IO memory mapping issue.  The IrDA port tries to grab two addresses
>> (0x2f8 and 0x2e8) but there's already two ports in use by the serial
>> module (0x3f8-physport and 0x2f8-modem).  So the IrDA modules does a
>> power grab, shuffles addresses and IRQs around and poof, no more serial
>> ports.  The toshsat1800-irdasetup program identifies the IrDA chip and
>> sees three serial ports.  I'm not sure why it sees three though but it
>> doesn't appear that I can change the IO port addresses.