From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: Greg KH <greg@kroah.com>
Cc: linux-serial@vger.kernel.org, matts@commtech-fastcom.com,
u.kleine-koenig@pengutronix.de
Subject: Re: [PATCH] serial/8250: Increase number of serial ports to 32
Date: Fri, 10 Dec 2010 16:10:30 +0100 [thread overview]
Message-ID: <4D0242E6.4070604@visionsystems.de> (raw)
In-Reply-To: <20101110173303.GA12830@kroah.com>
>>>> This will make sure that multiple serial port cards can be
>>>> used out of the box. Otherwise the user must pass
>>>> nr_uarts parameter, that will be often forgotten and increases
>>>> support requests for serial card vendors.
>>> Has this really happened in the past?
>> It is still the case. The most requests that we get are "the card
>> doesn't function under Ubuntu...". After examining dmesg one could see
>> that 8250 driver is initialized with 4 UARTS.
>>
>> There are also lots of questions and bugs concerning this subject.
>> Like this one:
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/125524. I even
>> found some entries from 2010:
>> http://www.gnulinux.in/forum/4-port-serial-card-installation-fedora-11
> Then get the distro to change the default setting of their kernels.
>
>>> What is the downside of changing
>>> this option that has been around for many years now? Also note that
>>> multi-port serial cards are more rare these days than they used to be so
>>> changing this seems a bit pointless now.
>> I can say that those cards are still selling. They're not dead.
>>
>> The downside is that those card are not working out of the box and
>> users not experienced in Linux often miss this parameter. Also some
>> Live Linuxes like Ubuntu (perhaps I missed something) don't provide
>> command line parameter, so you have to reload the driver with proper
>> parameter.
>>
>> I understand that it is somehow a responsibility of distribution
>> maintainers to properly configure the kernel, but I hope that if
>> vanilla kernel would increase default value, then they will also
>> follow.
> I doubt it as they would never notice that the value changed at all
> (they run 'make oldconfig'). So please just work with the distros that
> you are having problems with to get the value changed.
I just want to summarize the effort of increasing the number of run-time UARTs.
openSUSE and Ubuntu both accepted this change without long discussion:
https://bugzilla.novell.com/show_bug.cgi?id=652954
https://bugs.launchpad.net/ubuntu/+bug/675453
ReHat/Fedora rejected the change without really acceptable reason: https://bugzilla.redhat.com/show_bug.cgi?id=657530
By Debian is the question still in discussion: http://lists.debian.org/debian-kernel/2010/11/msg00211.html
Uwe pointed to the discussion about making 8250 UART detection dynamically: http://lists.debian.org/debian-kernel/2010/11/msg00286.html.
Yegor
next prev parent reply other threads:[~2010-12-10 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 13:54 [PATCH] serial/8250: Increase number of serial ports to 32 Yegor Yefremov
2010-11-10 16:08 ` Greg KH
2010-11-10 17:02 ` Yegor Yefremov
2010-11-10 17:33 ` Greg KH
2010-12-10 15:10 ` Yegor Yefremov [this message]
2010-11-10 19:10 ` Matt Schulte
2010-11-10 19:28 ` Greg KH
2010-11-10 21:28 ` Matt Schulte
2010-11-11 0:52 ` Greg KH
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=4D0242E6.4070604@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=greg@kroah.com \
--cc=linux-serial@vger.kernel.org \
--cc=matts@commtech-fastcom.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).