kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: nholland@tisys.org (Nils Holland)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Best way for PCI memory allocation?
Date: Thu, 18 Dec 2014 16:37:17 +0100	[thread overview]
Message-ID: <20141218153717.GA6467@triton374.startdedicated.com> (raw)
In-Reply-To: <20141218152459.GB73343@crux.local>

On Thu, Dec 18, 2014 at 10:24:59AM -0500, John de la Garza wrote:
> On Thu, Dec 18, 2014 at 02:32:17PM +0200, testlaster wrote:
> > Hey Guys.
> > What would you say is the best memory allocation function to use when I 
> > want to dump a specific size and address of memory to a file?
> > Im working through the PCI chip to gain access to a shared 8meg memory 
> > bank. What I essentially have to do is try and access that bank from 
> > memory start to a specific memory offset and
> > dump all its containing data into a file as soon as possible.
> 
> Consider creating a new thread instead of replying when you are
> changing the subject.  When you reply the your mail is still
> associated with the original topic (at least form some email clients).
> When you start a new thread it gets a new ID and will have its own
> thread.

...and while you're at it: Why not put your code on some webserver or
pastebin service / whatever if it is too long to include it in your
message? It might be of very much interest to people who'd like to
help you out! :-)

Greetings,
Nils

  reply	other threads:[~2014-12-18 15:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  1:28 How to submit for eudyptula-challenge wangyubin
2014-03-25  1:52 ` Masood Mehmood
2014-12-18  6:02   ` sanjeev sharma
2014-12-18  6:55     ` Fernando Apesteguía
2014-12-18 12:32       ` Best way for PCI memory allocation? testlaster
2014-12-18 15:24         ` John de la Garza
2014-12-18 15:37           ` Nils Holland [this message]
2014-12-18  6:58     ` How to submit for eudyptula-challenge Manish Katiyar
2014-12-18  7:09     ` Sudip Mukherjee
2014-12-18 12:32       ` Vinícius Tinti
2014-12-18 12:37         ` Lucas Tanure
2014-12-18 16:22           ` Jessica Ross
2014-12-19  4:30             ` sanjeev sharma
2014-03-25  1:59 ` Parinay Kondekar
2014-03-25  2:16 ` Aruna Hewapathirane
2014-03-25  2:42   ` wangyubin
2014-03-25  2:48     ` Aruna Hewapathirane
2014-03-25  3:08       ` wangyubin
2014-03-25  3:28         ` Aruna Hewapathirane
2014-03-25  4:47           ` wangyubin
2014-03-25  5:29             ` Pranay Srivastava

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=20141218153717.GA6467@triton374.startdedicated.com \
    --to=nholland@tisys.org \
    --cc=kernelnewbies@lists.kernelnewbies.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).