All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Smolik <marvin@mydatex.cz>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH 2.6.17 sparc64] 32-bit compat for Mach64 framebuffer
Date: Fri, 07 Jul 2006 07:30:19 +0000	[thread overview]
Message-ID: <44AE0D8B.5060805@mydatex.cz> (raw)
In-Reply-To: <200607060020.k660Krv1009111@harpo.it.uu.se>

David Miller napsal(a):
> From: Daniel Smolik <marvin@mydatex.cz>
> Date: Thu, 06 Jul 2006 21:35:43 +0200
> 
> 
>>I have similar problem with my Raptor GFX (Permedia2). If I run 
>>Xserver in fb driver I get this:
>>
>>
>>ioctl32(Xorg:13334): Unknown cmd fd(7) cmd(40584606){00} arg(ff25bb9c) 
>>on /dev/fb0
>>ioctl32(Xorg:13334): Unknown cmd fd(7) cmd(40184600){00} arg(ff25bba4) 
>>on /dev/fb0
>>
>>Is it same problem as in Atyfb ?
> 
> 
> Yes, it is the same problem.
> 
> And I've used ATI R128 cards without Sun firmware on them too,
> and they would cause the same messages.
> 
> It makes zero sense to put knowledge of this SBUS framebuffer
> ioctl into every single framebuffer driver, because that is what
> you would need to do in order to cover all possible cases.

Thanks for answer. But what can we do with this problem ? Start 
communicate with video driver authors ?


			Regards
				Dan

  parent reply	other threads:[~2006-07-07  7:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  0:20 [PATCH 2.6.17 sparc64] 32-bit compat for Mach64 framebuffer Mikael Pettersson
2006-07-06  0:20 ` Mikael Pettersson
2006-07-06  1:01 ` Antonino A. Daplas
2006-07-06  1:01   ` Antonino A. Daplas
2006-07-06 19:35 ` Daniel Smolik
2006-07-07  7:17 ` David Miller
2006-07-07  7:30 ` Daniel Smolik [this message]
2006-07-07  9:30 ` David Miller
2006-07-07 10:09 ` Daniel Smolik
2006-07-07 10:15 ` David Miller
2006-07-07 10:25 ` Daniel Smolik
2006-07-07 10:30 ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06  1:44 Mikael Pettersson
2006-07-06  1:44 ` Mikael Pettersson
2006-07-06  3:52 ` David Miller
2006-07-06  3:52   ` David Miller

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=44AE0D8B.5060805@mydatex.cz \
    --to=marvin@mydatex.cz \
    --cc=sparclinux@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 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.