All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir 'phcoder' Serbinenko <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Feature Request: 32-bit mem write and 'setpci -s' type command in menu.lst
Date: Fri, 23 Oct 2009 16:42:43 +0200	[thread overview]
Message-ID: <4AE1C0E3.1090506@gmail.com> (raw)
In-Reply-To: <4116f8730910230653s5f7e2bfatb17668ce91716ec@mail.gmail.com>

Nando wrote:
> Hi Vlad,
>
> Thank you for this! Just what I was looking for. With pciexbar I'll be
> able to do the equivalent of setpci by calculating the addresses
> needing memory writes.
Except pciconf space
>
> Another question -  is there any "write_dump" sort of command where  I
> can give an address, a file and it writes the binary data of the file
> at the starting address up to the EOF marker? Would help overcome my
> mPCIe whitelisting where i have a DOS workaround in place to do
> exactly that. I see there is hexdump and dump but neither appear to
> provide such function. If it doesn't exist, can a request be made to
> add it? eg:
>
> write_dump ADDRESS FILE
> eg: write_dump 0xF8000000  dump_file
>
This has already been discussed and conclusion that it's too dangerous
to write to FS from grub2. If it's one time operation you can just boot
FreeDOS for it. IF it's not explain why do you need it on every boot
> Nando
>
>
> On Thu, Oct 22, 2009 at 10:51 PM, Vladimir 'phcoder' Serbinenko
> <phcoder@gmail.com <mailto:phcoder@gmail.com>> wrote:
>
>     > write 0xFED93418 0xC330005
>     look at write_dword
>     >
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>   


-- 
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git 





  reply	other threads:[~2009-10-23 17:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 11:33 Feature Request: 32-bit mem write and 'setpci -s' type command in menu.lst Nando
2009-10-22 11:51 ` Vladimir 'phcoder' Serbinenko
2009-10-23 13:53   ` Nando
2009-10-23 14:42     ` Vladimir 'phcoder' Serbinenko [this message]
2009-10-24  8:42       ` Nando
2009-10-24  8:54         ` Vladimir 'phcoder' Serbinenko
2009-10-24 10:57           ` Seth Goldberg
2009-10-24  8:55         ` Bean
2009-12-22 16:27         ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-12-22 16:25 ` [PATCH] " Vladimir 'φ-coder/phcoder' Serbinenko

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=4AE1C0E3.1090506@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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.