linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robin Gilks <robin.gilks@tait.co.nz>
To: ppc embedded list <linuxppc-embedded@ozlabs.org>
Subject: 8xx UART TX > 8 data bits
Date: Wed, 13 Apr 2005 11:17:18 +1200	[thread overview]
Message-ID: <425C56FE.2020308@tait.co.nz> (raw)

Greetings

I'm trying to get an SMC channel to operate as a UART with more than 8 
data bits (13 in fact!!). Using a 2.4.22 kernel on a mpc859 (basic 866).

This means its going to be getting two half words from the BDs for each 
'character'. With the constraints of the SMC requiring even addresses 
etc for this mode of operation, does anyone know if it will work writing 
2x8 bit characters at a time so as to keep the existing tty structure 
for SMC handling?

I've tried tracing the tty layers by code inspection but I keep getting 
lost in the indirections!! If I could find how the BDs are allocated as 
a result of a character write, then perhaps I could make minor mods to 
ensure memory allocs on an even address.

Could be that I'm totally off the wall but I'm trying for a 'minimum 
effort' viability hack :-))

-- 
Robin Gilks
Senior Design Engineer          Phone: (+64)(3) 357 1569
Tait Electronics                Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks@tait.co.nz
New Zealand

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

                 reply	other threads:[~2005-04-12 23:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=425C56FE.2020308@tait.co.nz \
    --to=robin.gilks@tait.co.nz \
    --cc=linuxppc-embedded@ozlabs.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).