All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Mendoza <ricardo.mendoza@kanux.com>
To: linux-mips@linux-mips.org
Subject: [Fwd: Re: sharp mobilon hc-4100]
Date: Thu, 08 Jul 2004 16:03:10 -0400	[thread overview]
Message-ID: <40EDA87E.3060509@kanux.com> (raw)

Volker Jahns wrote:

> 
> Modifications are certainly a must:
> 
> e.g. 2.4.20 in drivers/video/tx3912fb.h thereis _only_  framebuffer definitions for the nino:
> <pre>
> #if defined(CONFIG_NINO_4MB) || defined(CONFIG_NINO_8MB)
> #define FB_X_RES       240 
> #define FB_Y_RES       320
> #if defined(CONFIG_FBCON_CFB4)
> #define FB_BPP         4
> </pre>
> 
> while 2.4.0-test9 carries the _good_ information for the velo 1, velo 500 and for the helio ( the code for the nino is missing here). In drivers/video/r3912fb.h ( which seems to be the historic version of tx3912fb.h, ouch what a chaos :-(
> <pre>
> #ifdef CONFIG_PHILIPS_VELO
> #       ifdef CONFIG_PHILIPS_VELO1
> #               define FB_X_RES         480
> #       elif defined(CONFIG_PHILIPS_VELO500)
> #               define FB_X_RES         640
> #       endif
> #       define  FB_Y_RES        240
> #       ifdef CONFIG_PHILIPS_VELO_4GRAY
> #               define FB_BPP   2
> #       else /* CONFIG_PHILIPS_VELO_16GRAY */
> #               define FB_BPP   4
> #       endif
> #       define FB_IS_GREY     1
> #       define FB_IS_INVERSE  0
> #       define VIDEORAM_SIZE  (FB_X_RES * FB_Y_RES * FB_BPP / 8)
> </pre>
> 
> On the other hand the mobilon needs 
> <pre>
> #               define FB_X_RES         640
> #               define FB_X_RES         240
> #               define FB_BPP           4
> </pre>
> 
> This information ( and what else which might be of interest to make the LCD working on this thing) must have get lost on the kernel's way. I really wonder where to find a more or less functional version of the kernel code to start with.
> 

The 2.4.17 tree on Steven J. Hill's website is functional, I can give it
  to you if you cant find it, just let me know.

By the way, when I refer to functional is for the TX3912 generic stuff,
one thing for sure is that you _WILL_ need to make an specific machine
directory for the mobilon, and you can use the same code for it, after
removing the non-generic tx3912 stuff and perhaps changing some stuff
that matters only to the mobilon.

You can also try hacking on the nino files as if you were using a nino.

P.D. Remove the html tags

-- 
Ricardo Mendoza Meinhardt
ricardo.mendoza@kanux.com

.knxTech
Administrador Linux
Programador/PHP

"get ready for a bit of the old Ultra Violence"

             reply	other threads:[~2004-07-08 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 20:03 Ricardo Mendoza [this message]
2004-07-09 11:21 ` [Fwd: Re: sharp mobilon hc-4100] Ralf Baechle
2004-07-09 15:46   ` Ricardo Mendoza

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=40EDA87E.3060509@kanux.com \
    --to=ricardo.mendoza@kanux.com \
    --cc=linux-mips@linux-mips.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.