From: vibisreenivasan <vibi_sreenivasan@cms.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-patches@ecos.sourceware.org
Subject: Re: Re: [PATCH]:add support for at91sam7x processor to work in different supported USART MODE
Date: Mon, 30 Mar 2009 08:27:00 -0000 [thread overview]
Message-ID: <1238402184.2203.30.camel@system> (raw)
In-Reply-To: <20090330081256.GJ17160@lunn.ch>
On Mon, 2009-03-30 at 10:12 +0200, Andrew Lunn wrote:
> On Mon, Mar 30, 2009 at 01:36:27PM +0530, vibisreenivasan wrote:
> > >> AT91sam7x hardware supports different usart configurations like
> > >> RS485,IrDA.
> > >> Patch helps that to be set during compile time.
> >
> > > Hi I don't really see how this helps. How do you change the mode? I
> > > don't see any current code which allows you to change this new mode
> > > field. Also, how do you handle baud rate generation? The different
> > > modes seem to calculate the baud rates using different formula. At
> > > the moment, i don't think this patch is useful.
> > > Andrew
> >
> > hi,
> > thanks for looking into this code.
> > We can set the MODE ONLY AT COMPILE TIME.
>
> How?
I am using the 485 mode by changing in the source code directly.
But planning to put it as a cdl option.
>
> > And i really missed the baud rate generation part.
>
> A lot depends on which mode you are using. Some modes do use the same
> baud as normal USART. Some not.
>
> > Can I add that & resubmit this again , will it be helpful?
>
> It is too early to say. Keep working on it and if it does become
> useful then yes. However, at the moment it is not useful.
>
> Andrew
>
THANKS FOR THE FEED BACK
Thanks & regards
vibi
>
next prev parent reply other threads:[~2009-03-30 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 7:57 vibisreenivasan
2009-03-30 8:13 ` Andrew Lunn
2009-03-30 8:27 ` vibisreenivasan [this message]
2009-03-30 8:45 ` Andrew Lunn
2009-03-30 12:26 ` vibisreenivasan
2009-04-05 11:39 ` vibisreenivasan
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=1238402184.2203.30.camel@system \
--to=vibi_sreenivasan@cms.com \
--cc=andrew@lunn.ch \
--cc=ecos-patches@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).