Novatel-Wireless U530/HP-ZD8004ap

Dominik Brodowski linux at dominikbrodowski.net
Thu Sep 22 15:12:17 EDT 2005


Hi,

On Thu, Sep 22, 2005 at 05:58:30PM +1000, Roger W. Brown wrote:
> The U530 has two serial ports.
> On inserting the U530, directories 0.0 and 0.1 appear
> under the yenta_cardbus directory:
> /sys/devices/pci0000\:00//0000:00:1e.0/0000:0b:00.0

Excellent, this means that the two sub-devices are detected correctly.

> An odd feature is that the "driver" entries are missing.

This means the driver was not bound to the device yet, or the binding
failed.

> I'm just learning about udev-rules and I am not confident with them,
> so to connect a driver, I added
> PCMCIA_DEVICE_MANF_CARD(0x00a4, 0x1aaf),
> to the serial_cs.c kernel code.  "device" links appeared in the
> appropriate /sys directories.

>  kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
>  kernel: ACPI: PCI Interrupt 0000:0b:00.0[A] -> GSI 16 (level, low) -> IRQ 16
>  kernel: Yenta: CardBus bridge found at 0000:0b:00.0 [103c:3082]
>  kernel: Yenta: ISA IRQ mask 0x0cf8, PCI irq 16
>  kernel: Socket status: 30000006
>  kernel: pcmcia: parent PCI bridge I/O window: 0x5000 - 0x5fff
>  kernel: cs: IO port probe 0x5000-0x5fff: clean.
>  kernel: pcmcia: parent PCI bridge Memory window: 0xc8200000 - 0xc82fffff
>  kernel: pcmcia: parent PCI bridge Memory window: 0x30000000 - 0x31ffffff
> 
>               ----  U530 card inserted here  ----
> 
>  kernel: cs: memory probe 0xc8200000-0xc82fffff: excluding 0xc8200000-0xc820ffff
>  kernel: ttyS0 at I/O 0x5100 (irq = 3) is a 16550A
>  kernel: serial_cs: no usable port range found, giving up
>  kernel: 0.1: RequestIO: No more items
> 
> I have tried to use "setserial" to reassign the ttyS0 irq but it did not help.

We need to distinguish here:

pcmcia0.0 - ttyS0 got loaded without problems, AFAICS. Why do you want to
reassign the IRQ? You can do that by adding "exclude irq 3" to
/etc/pcmcia/config.opts, but I do not see why you'd want to do that.

pcmcia0.1 - ttyS1 did not start, because it couldn't find appropriate
ioports in the resource database. What's in /etc/pcmcia/config.opts? Try
adding

include port 0x4000-0x4fff

to that file, and run /sbin/pcmcia-socket-startup manually.

	Dominik



More information about the linux-pcmcia mailing list