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 > <phco...@gmail.com <mailto:phco...@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 _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
