public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: henrique <henrique@cyclades.com>
To: Ed Vance <EdV@macrolink.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: A new serial baud rate
Date: Wed, 31 Jul 2002 09:37:39 -0300	[thread overview]
Message-ID: <200207310937.39301.henrique@cyclades.com> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A7908@EXCHANGE>

Hello !!!

FYI, I have done the changes on the kernel to include 14400 bps support. The 
modifications are:

- include/asm-ppc/termbits.h
	- create the define B14400 after B9600 and shift all defines after this.
- drivers/char/tty_io.c
	- add 14400 to baud_table

As you can see, I've done it for a PowerPC. I don't know if it is also quite 
simple for another arch's.

thanks for your feedback
regards
Henrique

On Friday 26 July 2002 01:00 pm, Ed Vance wrote:
> > > On Thu, July 25, 2002 at 12:14 PM, henrique wrote:
> > > > I just wanna know what is the procedure to insert this new baud
> > > > rate (14400) in the linux kernel.
> >
> > On Thu, July 25, 2002 at 2:36 PM, Ed Vance wrote:
> > > If you have a 2.4.x kernel, and your serial ports have "simple"
> > > UARTs like a 16550A, then use the setserial command to directly
> > > set the UART's divisor. See the man page on setserial, which also
> > > has words about how to put the setserial commands into a script
> > > that runs automatically when you boot the system.
> > >
> > > You will have to know the "baud base" rate of your UARTs. This is
> > > the baud rate that you get if you set the divisor to 1 (probably
> > > 115200 bps).
> > >
> > > The new divisor is baud_base / 14400 (which is probably 8).
>
> On Fri, July 26, 2002 at 6:15 AM, henrique wrote:
> > Ed, unfortunately my equipment uses the 2.2.14 kernel.
> > Does your suggestion work in such kernel ? It would be
> > the easiest way to solve this.
>
> Hi Henrique,
>
> I know of no specific reason why it would not work under 2.2. I just
> have no direct experience with the 2.2 kernel and the corresponding
> version of the serial driver. If the setserial functionality that I
> described is in your setserial man page from 2.2, then I think the
> method should work well.
>
> Best regards,
> Ed
>
> ----------------------------------------------------------------
> Ed Vance              edv@macrolink.com
> Macrolink, Inc.       1500 N. Kellogg Dr  Anaheim, CA  92807
> ----------------------------------------------------------------

  reply	other threads:[~2002-07-31 12:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26 16:00 A new serial baud rate Ed Vance
2002-07-31 12:37 ` henrique [this message]
     [not found] <1779CCD227485B49A825718AAAA90E3E406CD4@tpsmail01.turbopower.net>
2002-07-26 13:14 ` henrique
  -- strict thread matches above, loose matches on Subject: below --
2002-07-25 21:35 Ed Vance
     [not found] <1779CCD227485B49A825718AAAA90E3E406CD1@tpsmail01.turbopower.net>
2002-07-25 19:14 ` henrique
2002-07-25 19:40   ` Neil Everton
2002-07-25 19:45   ` Matti Aarnio
2002-07-25 18:22 henrique
2002-07-25 18:46 ` Mike Dresser
2002-07-25 19:35 ` Matti Aarnio

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=200207310937.39301.henrique@cyclades.com \
    --to=henrique@cyclades.com \
    --cc=EdV@macrolink.com \
    --cc=linux-serial@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