From: Peter Korsgaard <jacmet@sunsite.dk>
To: John Linn <John.Linn@xilinx.com>
Cc: linux-serial@vger.kernel.org, grant.likely@secretlab.ca,
michal.simek@petalogix.com, john.williams@petalogix.com
Subject: Re: [PATCH] uartlite: move from byte accesses to word accesses
Date: Wed, 20 Jan 2010 23:53:29 +0100 [thread overview]
Message-ID: <87y6jsl76e.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <2f45ae30-3c9f-4b92-90a1-fc6a2a91445b@SG2EHSMHS006.ehs.local> (John Linn's message of "Wed, 20 Jan 2010 14:49:45 -0700")
>>>>> "John" == John Linn <John.Linn@xilinx.com> writes:
Hi,
>> Why is it less desired?
John> We are wanting to use our IP cores over a PCIe bus and it only
John> allows 32 bit accesses.
Ok, that's valuable information for the commit messages.
John> I understand. Most of our customers are using a 32 bit bus so
John> that this wouldn't be a problem for most people.
John> We could do some kind of conditional compilation for the
John> accesses, but it's certainly less desired. We could make 32 bit
John> the default and then allow a kernel config to change the access
John> size.
Naah, the project where we needed 16bit access is _OLD_, and the
platform hasn't been ported from arch/ppc, so let's just move to 32bit
access.
If you send an updated patch with a more detailed commit message then
I'll ack it.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-01-20 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 16:45 [PATCH] uartlite: move from byte accesses to word accesses John Linn
2010-01-20 19:23 ` Peter Korsgaard
2010-01-20 21:49 ` John Linn
2010-01-20 22:53 ` Peter Korsgaard [this message]
2010-01-20 22:57 ` John Linn
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=87y6jsl76e.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=John.Linn@xilinx.com \
--cc=grant.likely@secretlab.ca \
--cc=john.williams@petalogix.com \
--cc=linux-serial@vger.kernel.org \
--cc=michal.simek@petalogix.com \
/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