From: Robert Woerle <robert@paceblade.com>
To: root@chaos.analogic.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: serial.c - start looking from 0x220 iomem_base ??
Date: Mon, 16 Feb 2004 17:13:55 +0100 [thread overview]
Message-ID: <4030EC43.90605@paceblade.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0402131025120.4338@chaos>
Richard B. Johnson schrieb:
>On Fri, 13 Feb 2004, Robert Woerle wrote:
>
>
>
>>Hi
>>
>>I am having here a device (Tablet PC ) sample with a serial resistive
>>touchscreen .
>>Under Windows it comes up as COM1 at IO-Base 0x220 -0x227 IRQ 4 .
>>Now it seems that in linux the serial driver doesnt look for so "low"
>>I/O-Base `s .
>>
>>By hacking around by hardcoding the 0x220 somehwere in serial.c i get it
>>to detect a standard 16550 , but
>>unfortunately it then assumes that all ttySX have this base .
>>This is because of my hardcoded hack and the driver not looking for all
>>the rest mem bases.
>>
>>So the quesion is :
>>Where do i tell serial.o to start lower ( at 0x220 ) to look for
>>controllers .. .??
>>
>>
>>
>>Pls also CC me directly since i am only monitoring this list .
>>
>>
>
>There are 4 de facto standard serial ports:
>
>COM1 0x3F8 IRQ4
>COM2 0x2F8 IRQ3
>COM3 0x3E8 IRQ4
>COM4 0x2E8 IRQ3
>
>If you have a port at 0x220, it is above the game-port area,
>but not where the kernel should "look for" serial devices.
>Therefore, you don't tell the kernel to, as you state, start
>lower. Instead, you tell the kernel where they are by putting
>them in the pnp_devices[] table.
>
>
>
>
I tryed that now and added a device like
ISAPNP_VENDOR('P', 'N', 'P'), ISAPNP_DEVICE(0x0220),
but nothing happens ... it leaves the function saying
<7>"Leaving probe_serial_pci() (probe finished)
What can i do ?
prev parent reply other threads:[~2004-02-16 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 15:09 serial.c - start looking from 0x220 iomem_base ?? Robert Woerle
2004-02-13 15:36 ` Richard B. Johnson
2004-02-16 16:13 ` Robert Woerle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4030EC43.90605@paceblade.com \
--to=robert@paceblade.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.