From: tytso@valinux.com
To: lukasz@lt.wsisiz.edu.pl
Cc: twaugh@redhat.com, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: [patch] 2.2.18 PCI_DEVICE_ID_OXSEMI_16PCI954
Date: Sun, 17 Dec 2000 02:18:36 -0800 [thread overview]
Message-ID: <E147ato-0006CZ-00@beefcake.hdqt.valinux.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012170143360.4003-100000@lt.wsisiz.edu.pl> (message from Lukasz Trabinski on Sun, 17 Dec 2000 01:51:15 +0100 (CET))
In-Reply-To: <Pine.LNX.4.30.0012170143360.4003-100000@lt.wsisiz.edu.pl>
Date: Sun, 17 Dec 2000 01:51:15 +0100 (CET)
From: Lukasz Trabinski <lukasz@lt.wsisiz.edu.pl>
OK, You have right, I'm not a driver programmer, but it probably should
look like this:
+#define PCI_DEVICE_ID_OXSEMI_16PCI954 0x9501
That's correct, yes. The reason why the original poster was having
problems was that the serial_compat.h defined PCI_VENDOR_ID_OXSEMI
PCI_DEVICE_ID_OXSEMI_16PCI954 if PCI_VENDOR_ID_OXSEMI was not defined.
Since 2.2.18 defines PCI_VENDOR_ID_OXSEMI, but ..._OXSEMI_16PCI954, the
5.05 serial.c wouldn't compile.
When we integrate a newer serial driver into 2.2.19, I'll include the
necessary patches to pci_ids.h.
Why serial.c from the 2.2.18 not support 921600 speed? We have to patch
it...
2.2.18 has an old serial driver that doesn't know about PCI devices.
The updated serial driver available at http://serial.sourceforge.net
should deal with this correctly.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-17 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 20:57 Lukasz Trabinski
2000-12-15 23:04 ` Bruce Korb
2000-12-16 23:21 ` Tim Waugh
2000-12-17 0:51 ` Lukasz Trabinski
2000-12-17 10:18 ` tytso [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=E147ato-0006CZ-00@beefcake.hdqt.valinux.com \
--to=tytso@valinux.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz@lt.wsisiz.edu.pl \
--cc=twaugh@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®