All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: gnewsense-dev <gnewsense-dev@nongnu.org>,
	The development of GRUB 2 <grub-devel@gnu.org>,
	loongson-dev@googlegroups.com,
	rms / fsf sysadmin / fsf volunteers / lemote <lemote@gnu.org>,
	Danny Clark <djbclark@freedomincluded.com>
Subject: Re: [loongson-dev] Fuloong liberated
Date: Mon, 16 May 2011 19:02:10 +0200	[thread overview]
Message-ID: <4DD15892.9060405@gmail.com> (raw)
In-Reply-To: <20110516220523.77082d8a@natsu>

[-- Attachment #1: Type: text/plain, Size: 2540 bytes --]

On 16.05.2011 18:05, Roman Mamedov wrote:
> On Mon, 16 May 2011 11:12:42 +0200
> Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> wrote:
>
>> Hello all. As you all probably know the Floong as shipped by lemote uses
>> a 64K binary blob to initialize the video which makes it non-free.
>> Fortunately now there is an alternative: GRUB2.
> Hello,
>
> So you are replacing PMON with GRUB2, but are you sure the video BIOS is also
> removed by this operation?
I believe so. I couldn't find any other flash chip which could contain
it. The video chip is soldered on the board and has no flash nearby. The
Video BIOS I reverse engineered was recovered from pmon source tree. So
I suppose it is eradicated.
>  And then, is it GRUB2 that initializes the video
> chip instead of SiS BIOS, setting up VRAM timings, the video output, screen
> mode, etc? Does it actually have special code for bringing up the SiS 315E?
>
Yes. It wasn't easy to figure out the right sequence to bring CR
(controller) up. Currently the only supported resolution is 640x480x8
and the parameters are precomputed. While not the nicest resolution it
should work with any monitor and is enough to show console (or menu).
Linux is able to change to any mode afterwards.
>> To generate firmware
>> image do:
>> bzr branch http://bzr.savannah.gnu.org/r/grub/trunk/grub
>> cd grub
>> ./configure --target=mipsel --with-platform=loongson
>> make
>> ./grub-mkimage -C xz -O mipsel-fuloong-flash -o grub.img -d grub-core/
>> normal linux ata usb_keyboard ohci part_msdos ext2 xfs part_gpt ls halt
>> reboot usbms gzio
> Can you perhaps post a compiled firmware somewhere.
>
Sorry but I'm on my way now and I don't have fuloong under my hand. I
could post the latest image that worked for me but it has no support for
compressed kernel (I didn't include gzio module)
>> The resulting grub.img can be flashed using flashrom
>> http://flashrom.org/Flashrom. Be sure to have backup chip before
>> flashing.
> Also I believe it should be possible to chain-load this image from PMON for
> testing, via the "load <filename>" command, and then "g".
>
Not this image. Image generated with -O mipsel-fuloong-flash has to be
flashed (it can start only from ROM and at fixed address). To generate
loadable image replace -O mipsel-fuloong-flash with -O
mipsel-fuloong-elf. It will create an image which is the same as ROM
image but in ELF format and without fwstart.S part.


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]

  reply	other threads:[~2011-05-16 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16  9:12 Fuloong liberated Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-16 16:05 ` [loongson-dev] " Roman Mamedov
2011-05-16 17:02   ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-05-16 17:36 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-16 19:45 ` 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=4DD15892.9060405@gmail.com \
    --to=phcoder@gmail.com \
    --cc=djbclark@freedomincluded.com \
    --cc=gnewsense-dev@nongnu.org \
    --cc=grub-devel@gnu.org \
    --cc=lemote@gnu.org \
    --cc=loongson-dev@googlegroups.com \
    --cc=rm@romanrm.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 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.