From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] PCI serial card support
Date: Sat, 08 Nov 2008 14:23:32 +0200 [thread overview]
Message-ID: <491584C4.5020407@nic.fi> (raw)
In-Reply-To: <20081108112536.GA11583@thorin>
Robert Millan wrote:
> On Fri, Nov 07, 2008 at 06:52:21PM +0200, Vesa Jääskeläinen wrote:
>> n0ano@n0ano.com wrote:
>>> Bad news, I heard back from the two people who wrote the PCI serial
>>> code for Linux (Russell King & Ted Tso) and they both agree that,
>>> no matter how the ambiguity got into the Linux source files, their
>>> intent was that the code was GPL v2 only.
>>>
>>> That being the case, we can't use the code and I don't want to try
>>> and re-write it from scratch so we're back to having the user manually
>>> specify the I/O port address but at least I can create a PCI ID table
>>> to map the base baud.
>> Ok. Then I would suggest that only simple change is made at this time to
>> support it. So we start from scratch on that implementation. Anyway...
>> it can be improved later on.
>
> Why not use PCI ID to support this particular card? This way Donald doesn't
> have to support all cards, but the base is laid out so more cards can be added
> in the future.
I have nothing against that. But in any case I think there has to be
this override functionality support. Just make it a bit harder for user
to type so they know it is advanced feature :). Making these transparent
for user is always a plus.
I just feel that it might be a bit overkill to chain this module to pci
module. Of course you can dynamically check if PCI module is there and
then ask identification information from there. If you make it other way
around so that some other module references to serial module and then
just registers new serial device there then that is better of course.
isnmod pciserial [device location in system, or if omitted, autodetect]?
next prev parent reply other threads:[~2008-11-08 12:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 0:38 [PATCH] PCI serial card support donald.d.dugger
2008-11-04 15:39 ` Robert Millan
2008-11-04 18:24 ` Dugger, Donald D
2008-11-05 9:58 ` Robert Millan
2008-11-05 15:37 ` Dugger, Donald D
2008-11-06 15:02 ` Robert Millan
2008-11-06 15:28 ` Dugger, Donald D
2008-11-06 16:06 ` Robert Millan
2008-11-06 16:30 ` Dugger, Donald D
2008-11-06 17:00 ` Dugger, Donald D
2008-11-07 16:07 ` n0ano
2008-11-07 16:52 ` Vesa Jääskeläinen
2008-11-08 11:25 ` Robert Millan
2008-11-08 12:23 ` Vesa Jääskeläinen [this message]
2008-11-08 12:45 ` Robert Millan
2008-11-08 14:00 ` Vesa Jääskeläinen
2008-11-09 1:58 ` n0ano
2008-11-09 21:57 ` Robert Millan
2008-11-09 22:13 ` Vesa Jääskeläinen
2008-11-09 22:14 ` n0ano
2008-11-12 18:58 ` n0ano
2008-11-13 18:05 ` Vesa Jääskeläinen
2008-11-13 20:13 ` n0ano
2008-11-14 19:24 ` n0ano
2008-11-22 2:53 ` Neo Jia
2008-11-22 7:18 ` Vesa Jääskeläinen
2008-11-04 18:26 ` Vesa Jääskeläinen
2008-11-04 18:38 ` Dugger, Donald D
2009-07-21 8:11 ` tony.gugo
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=491584C4.5020407@nic.fi \
--to=chaac@nic.fi \
--cc=grub-devel@gnu.org \
/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.