public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: mike <localgost@gmail.com>
To: Emmanouel Vasilakis <evas@agn.forthnet.gr>
Cc: linux-m68k@vger.kernel.org
Subject: Re: cirrusfb not working?
Date: Fri, 16 Jan 2009 19:11:26 +0100	[thread overview]
Message-ID: <8259f0250901161011t24eb0351l6b39739f0a20179@mail.gmail.com> (raw)
In-Reply-To: <49706C81.7000905@agn.forthnet.gr>

Try cirrusfb:640x480 or something


Default video modes
-------------------
At the moment, there are two kernel command line arguments supported:

mode:640x480
mode:800x600
	or
mode:1024x768

Full support for startup video modes (modedb) will be integrated soon.


2009/1/16 Emmanouel Vasilakis <evas@agn.forthnet.gr>:
> Hi,
>
> I was trying a few days ago to boot a recent 2.6 kernel on my Amiga 3000.
>
> From what I found online, in order to get a framebuffer display from my
> Picasso IV, I needed to use the cirrusfb driver to the kernel which replaced
> the older clgen driver (In latest 2.6 kernels).
>
> I tried stuff like:
>
> amiboot -k vmlinuz video=cirrusfb:
>
> No matter what I append to the video parameter, I can never get a display
> from the graphics card, it always comes up from the native ECS. Kernel
> messages say that a cirrusfb supported card was found. I was then told that
> cirrusfb does not work as expected, so any information on that?
>
> What eventually worked somehow, was: video=amifb:off, which produced a
> display from the Picasso, but was full of garbage.
>
> Thanks,
> Emmanuel
> --
> To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2009-01-16 18:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16 11:16 cirrusfb not working? Emmanouel Vasilakis
2009-01-16 18:11 ` mike [this message]
2009-01-17 10:30   ` Emmanuel Vasilakis
2009-01-18  2:25     ` mike

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=8259f0250901161011t24eb0351l6b39739f0a20179@mail.gmail.com \
    --to=localgost@gmail.com \
    --cc=evas@agn.forthnet.gr \
    --cc=linux-m68k@vger.kernel.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