linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve Spano" <steve@flconsult.com>
To: "'Antonino A. Daplas'" <adaplas@gmail.com>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: ##3 Frame Buffer Questions?
Date: Fri, 18 Aug 2006 22:43:08 -0400	[thread overview]
Message-ID: <015101c6c339$41a607b0$6400a8c0@fleballnchain> (raw)
In-Reply-To: <1155946775.9630.5.camel@daplas.org>

Hi Antonino,

We got the buffer working and showing now in the proc folder

So we can now do a cat random > fb0 - and that works.

Do you (or someone) know the correct pattern of magic #defines that will
put the console up on the VGA? I would like to see the startup
messages/login prompt on the VGA display.

Thanks!

Steve Spano, President
Finger Lakes Engineering
119 South Cayuga #200
Ithaca, Ny 14850
(V) 607-277-1614 x223
(C) 607-342-1150
www.FL-ENG.com - FLE's Main Website 
www.FLEDEVFORUM.com - FLE's Developer Forum

-----Original Message-----
From: Antonino A. Daplas [mailto:adaplas@gmail.com] 
Sent: Friday, August 18, 2006 8:20 PM
To: steve@flconsult.com; linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [Linux-fbdev-devel] ##3 Frame Buffer Questions?

On Fri, 2006-08-18 at 10:30 -0400, Steve Spano wrote:
> Hi Folks,
> 
>  
> 
> I have a question.
> 
> 
> Working on a "semi-custom" frame buffer for a Xilinx FPGA with the
> Microblaze.
> 
>  
> 
> The specific file we started with is already in the
> uclinux/drivers/video and is called xilinxfb.c
> 
>  
> 
> We can register the driver and a debug trace in the driver shows that
> it registers as FB0 29-0, so that should be right.
> 
>  
> 
> However, if I do a cat /dev/fb0  the linux responds by saying it can't
> open the device. It appears that somehow the default file pointer in
> dev/fb0 cannot connect to the actual driver?
> 
>  
> 
> MKNODing the driver also fails.
> 
>  
> 
> I do have other drivers that we have made that do install, so this
> isn't the first attempt at a driver.
> 
>  
> 
> Any thoughts on where I may look for some ideas on this?

What kernel version are you using?
Does it show up in /proc/fb? If it does, the device node it's bound too
should also show up.

If it does show up in /proc/fb, then make sure that info->screen_base
(in 2.6) or info->disp->screen_base (in 2.4) is pointing to the virtual
address of the framebuffer.

If publicly available, can you point us to the source?

Tony








-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-08-19  2:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 14:30 ##3 Frame Buffer Questions? Steve Spano
2006-08-19  0:19 ` Antonino A. Daplas
2006-08-19  2:43   ` Steve Spano [this message]
2006-08-19  9:44     ` Antonino A. Daplas
2006-08-19 19:46       ` Steve Spano

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='015101c6c339$41a607b0$6400a8c0@fleballnchain' \
    --to=steve@flconsult.com \
    --cc=adaplas@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).