mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nameer Yarkon <nameer.yarkon@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	Andi Kleen <andi@firstfloor.org>,
	Robert Hancock <hancockrwd@gmail.com>,
	"Anton D. Kachalov" <mouse@mayc.ru>,
	linux-kernel@vger.kernel.org
Subject: Re: Reading /dev/mem by dd
Date: Tue, 16 Feb 2010 10:35:40 +0200	[thread overview]
Message-ID: <bec9a5871002160035v63cce8ck9ecb9252b2f162a6@mail.gmail.com> (raw)

On Thu, Nov 12, 2009 at 8:13 PM, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> Is that the only valid use of /dev/mem, or even its main use?
>
> These days it is the primary use. Things like X11 were historically
> probably the biggest user of it, and things like LRMI sometimes need that
> sort of stuff.

how does X11 get now direct access to the physical memory (instead of
/dev/mem) ?

             reply	other threads:[~2010-02-16  8:35 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  8:35 Nameer Yarkon [this message]
2010-02-16  8:41 ` Andi Kleen
2010-02-16  9:03   ` Nameer Yarkon
2010-02-16 12:31 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2009-11-11 14:36 Anton D. Kachalov
2009-11-11 16:20 ` Américo Wang
2009-11-12 15:46   ` Anton D. Kachalov
2009-11-11 21:09 ` Robert Hancock
2009-11-12  2:12   ` Henrique de Moraes Holschuh
2009-11-12 11:09     ` Alan Cox
2009-11-12 16:06       ` Henrique de Moraes Holschuh
2009-11-12 17:52         ` Alan Cox
2009-11-12 16:44     ` Andi Kleen
2009-11-12 17:37       ` Henrique de Moraes Holschuh
2009-11-12 17:49         ` Alan Cox
2009-11-12 17:57           ` Henrique de Moraes Holschuh
2009-11-12 18:13             ` Alan Cox
2009-11-12 20:02               ` Henrique de Moraes Holschuh
2009-11-12 20:06                 ` Alan Cox
2009-11-12 21:07         ` Krzysztof Halasa
2009-11-12 21:29           ` Cyrill Gorcunov

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=bec9a5871002160035v63cce8ck9ecb9252b2f162a6@mail.gmail.com \
    --to=nameer.yarkon@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andi@firstfloor.org \
    --cc=hancockrwd@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mouse@mayc.ru \
    /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

all inboxes | Powered by JetHome®