All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Cooksey <thomas.cooksey@trolltech.com>
To: linux-embedded mailing list <linux-embedded@vger.kernel.org>
Subject: Re: Getting physical addresses of mmap'd pages from userspace
Date: Tue, 14 Oct 2008 08:36:26 +0200	[thread overview]
Message-ID: <200810140836.27710.thomas.cooksey@trolltech.com> (raw)
In-Reply-To: <20081013160927.GC9852@pengutronix.de>

On Monday 13 October 2008 18:09:27 Robert Schwebel wrote:
> On Mon, Oct 13, 2008 at 11:58:20AM -0400, George G. Davis wrote:
> > It comes down to decisions of bill-of-materials and performance, the
> > MBX/SGX options mentioned already are part of the SoCs and have high
> > bandwidth connections to the processor. External options increase cost
> > and won't match bandwidth of on chip options, but that's just my
> > ignorant opinion w/o looking at the low-level detail comparisons.
> > Unless you intend to encourage the SoC vendors to use the SM50x
> > instead?  : )  Of course, that won't help for the current and planned
> > generation(s) of devices...
> 
> The BoM argument is probably true for high volume consumer or automotive
> use cases. For industrial usage, long term maintainability and thus
> availability of documentation and code is usually a more important
> argument.
> 
> Just my 0.02 ct. I'm just a poor open source guy :)

<RANT>
What I don't understand is that I'm trying to do some pretty interesting & cool
stuff with their processors (of course I would say that!), which will probably
help them sell more units. Why then do they make it so difficult to work with
them? It feels like they're shooting themselves in the foot. Madness.
</RANT>

Cheers,

Tom

  reply	other threads:[~2008-10-14  6:36 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 16:15 Getting physical addresses of mmap'd pages from userspace Tom Cooksey
2008-10-10 16:37 ` Bart Van Assche
2008-10-10 19:12 ` Robert Schwebel
2008-10-13  6:33   ` Tom Cooksey
2008-10-13  7:00     ` Robert Schwebel
2008-10-13  7:20       ` Tom Cooksey
2008-10-13  7:28       ` Thomas Petazzoni
2008-10-13  7:31         ` Robert Schwebel
2008-10-13 12:50       ` Bill Gatliff
2008-10-13 13:23         ` Robert Schwebel
2008-10-13 15:58           ` George G. Davis
2008-10-13 16:09             ` Robert Schwebel
2008-10-14  6:36               ` Tom Cooksey [this message]
2008-10-14 15:47                 ` Bill Gatliff
2008-10-15  7:06                   ` Tom Cooksey
2008-10-15  8:30                     ` James Chapman
2008-10-15 18:27                   ` Robert Schwebel
2008-10-15 18:29                     ` Bill Gatliff
2008-10-13  9:37     ` Gilad Ben-Yossef
     [not found]     ` <48F31155.6090603@codefidence.com>
2008-10-13  9:38       ` Tom Cooksey
2008-10-13 12:48     ` Bill Gatliff
2008-10-13 14:45       ` Tom Cooksey
2008-10-13 15:09         ` Daniel THOMPSON
2008-10-13 17:21           ` George G. Davis
2008-10-13 17:29     ` Chris
2008-10-14  6:46       ` Tom Cooksey
2008-10-14  7:31     ` Daniel J Laird
2008-10-14  9:03       ` Tom Cooksey

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=200810140836.27710.thomas.cooksey@trolltech.com \
    --to=thomas.cooksey@trolltech.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.