From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N1cO4-0000Eh-NY for mharc-grub-devel@gnu.org; Sat, 24 Oct 2009 04:54:12 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N1cO2-0000E3-7X for grub-devel@gnu.org; Sat, 24 Oct 2009 04:54:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N1cO1-0000DR-0j for grub-devel@gnu.org; Sat, 24 Oct 2009 04:54:09 -0400 Received: from [199.232.76.173] (port=44801 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N1cO0-0000DM-Dl for grub-devel@gnu.org; Sat, 24 Oct 2009 04:54:08 -0400 Received: from fg-out-1718.google.com ([72.14.220.158]:38571) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N1cNz-0002Jw-PQ for grub-devel@gnu.org; Sat, 24 Oct 2009 04:54:08 -0400 Received: by fg-out-1718.google.com with SMTP id 16so3718375fgg.12 for ; Sat, 24 Oct 2009 01:54:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=/Rcz/SVLYxrKZuY2CDEB7Yb+TCUCPhpzWL8ZcEmklt8=; b=R2i8GunCASwp5IYmPFI9bQ2pFGmYoDIVJ9Qqlr6VeWrtAGuLGmBoP8fzrUiC16ICUn pGy3jqEtczDR/EOoiTC/vhluoC6WQaudJJQbzop0G0lsN11FlVLph9WGwpyEzTrFVdfe PdncHkj8wL+/5YDFdp+cGnFNkl6F7jGkw1EdU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=lPHXVouODEFzG9y+kOYYlh7RSem8hv2O0EK21Mvh1peu6QwwYNyx7dGEQrcAa6GjIm dhks6riRHX4XqwYMfh2CrnfCEH/cbGorBtVtQ7Dlhn1D6LmXLdAUCyLOlQurtR5nrbmI GeKEtCVSPP1zKfsT2sF6MRlGR/lw/2UnXP/NI= Received: by 10.86.203.35 with SMTP id a35mr1696955fgg.44.1256374445344; Sat, 24 Oct 2009 01:54:05 -0700 (PDT) Received: from debian.bg45.phnet (143-106.76-83.cust.bluewin.ch [83.76.106.143]) by mx.google.com with ESMTPS id 4sm404054fge.29.2009.10.24.01.54.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 24 Oct 2009 01:54:04 -0700 (PDT) Message-ID: <4AE2C0AB.1030905@gmail.com> Date: Sat, 24 Oct 2009 10:54:03 +0200 From: Vladimir 'phcoder' Serbinenko User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20090701) MIME-Version: 1.0 To: The development of GRUB 2 References: <4116f8730910220433ga7d2237q8a72589713c13d94@mail.gmail.com> <4AE0475F.2050107@gmail.com> <4116f8730910230653s5f7e2bfatb17668ce91716ec@mail.gmail.com> <4AE1C0E3.1090506@gmail.com> <4116f8730910240142l35f0c204t1c6d5dcb0ca7bcd6@mail.gmail.com> In-Reply-To: <4116f8730910240142l35f0c204t1c6d5dcb0ca7bcd6@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: Feature Request: 32-bit mem write and 'setpci -s' type command in menu.lst X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Oct 2009 08:54:10 -0000 Nando wrote: > Hi Vlad, > > > able to do the equivalent of setpci by calculating the addresses > > needing memory writes. > > Except pciconf space > > > Are you saying that write_dword will not write to pciconf space? pciconf space on x86 is acessible through inw/outw and not through memory > > > > > > 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 > > > I've like *read* a dump file into pciexbar memory space to overcome my > wifi whitelisting. Currently doing this via a grub2 DOS Image entry > explained at http://www.wimsbios.com/phpBB2/topic9388-135.html#53650 . > To have such an ability would mean I could just add another menuitem > "Ubunto [reverse whitelisting]" and bypass the need for the DOS > bootimage. This ability would be further enhanced if a compressed dump > file could be used to speed up the process. > > So I guess it should be a request for: > > - 'read_dump ADDRESS FILE' for mPCIe wifi whitelsting could be done > within grub2. . > - a 'setpci' type command to do pci-e pci-port bridge window fixups, > amongst other things. > Then I'm ok with it but this link doesn't provide technical info on how it was done. It looks a bit like it's changing acpi tables, if it's the case grub2 is already able to do this with 'acpi' command. What are first bytes of dump? > Nando > ------------------------------------------------------------------------ > > _______________________________________________ > 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