From: Paul Smith <paul@mad-scientist.net>
To: linux-embedded@vger.kernel.org
Subject: Re: Can I manage/modify console baud rates from userspace?
Date: Sun, 02 May 2010 12:14:55 -0400 [thread overview]
Message-ID: <1272816895.27961.1131.camel@homebase> (raw)
In-Reply-To: <4BDD4CC7.3050507@gmail.com>
On Sun, 2010-05-02 at 11:58 +0200, Marco Stornelli wrote:
> 02/05/2010 02:02, Paul Smith wrote:
> > I've looked at setserial and it supports a baud_base parameter but that
> > doesn't appear to be what I want (I tried it anyway: changing it didn't
> > work, my console output was still screwed up).
> >
> > Trying to do something like creating customized PXE configs on the
> > server based on the MAC addresses of the blades that are "new" (or old)
> > would be an absolute nightmare as people swap blades between chassis,
> > add new ones, etc. all the time.
> >
> >
> > Please help me find a better way... :-(
> >
>
> It's strange that it's not possible to change the baud rate, but I'm not
> an expert of tty layer. A naive implementation could be patch the kernel
> to choose a well-known baud rate for your hw reading a revision register
> or something like that.
I guess; I'd hate to have to modify the kernel like that though. Plus,
as far as I'm aware at the moment the only way to tell these blades
apart is through querying IPMI which would be a serious bummer to try to
do via the kernel, I believe. Maybe there's some other way to do it
that's simpler.
Still hoping someone will say "all you have to do is XYZZY..." Anyone?
next prev parent reply other threads:[~2010-05-02 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 0:02 Can I manage/modify console baud rates from userspace? Paul Smith
2010-05-02 9:58 ` Marco Stornelli
2010-05-02 16:14 ` Paul Smith [this message]
2010-05-02 20:25 ` Sam Ravnborg
2010-05-03 17:28 ` Paul Smith
2010-05-03 19:17 ` Alan Cox
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=1272816895.27961.1131.camel@homebase \
--to=paul@mad-scientist.net \
--cc=linux-embedded@vger.kernel.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 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).