/dev/fb device files are not created.

/dev/fb device files are not created.

[Jaap van den Handel]

Hi, 

I'm still working on the frame buffer driver for the vga solution my company  
has developed. I created a test program which prints the memory addresses.

When I tried to run the test program I found out that suddenly
the /dev/fb* files are not created anymore when the driver registers itself.

when I create the files manually, the vfb.o and our own driver both seem to 
return address 0x00000003 I think this cannot be ok.

Is there somebody who knows what the problem might be?

Thanks in advance
Jaap van den Handel



Confidentiality Note:
This e-mail and any attachments are confidential and the information herein
is property of Quest Innovations B.V.. If you are not the intended recipient(s) of this e-mail,you are hereby notified that any dissemination, distribution, 
copying, use of or reliance upon the information contained within this e-mail 
or attachments is unauthorized and strictly prohibited. If you have received
this e-mail in error, please notify us immediately by returning it to the
sender and delete this copy from your system.

Quest Innovations B.V.


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com

Re: /dev/fb device files are not created.

[Jan-Benedict Glaw]

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

On Sat, 2004-06-26 12:58:25 +0200, Jaap van den Handel <jaap@quest-innovations.com>
wrote in message <1088247505.40dd56d1e5047@webmail.quest-innovations.com>:
> I'm still working on the frame buffer driver for the vga solution my company  
> has developed. I created a test program which prints the memory addresses.

Where's actual source code for that? What kind of device is that? PCI
based? Is it used on PCs? I've never ever seen that piece of hardware,
there's no pointer to hardware docs, not even a name for that device
so that anybody could google for it...

> when I create the files manually, the vfb.o and our own driver both seem to 
> return address 0x00000003 I think this cannot be ok.

Right, looks wrong. From all the data provided about the device and it's
driver, the best guess for a base address is to read
(BITS_PER_LONG == 32? 4: 8) bytes from /dev/random...

> Is there somebody who knows what the problem might be?

Not until you put source code on the table and...

> Confidentiality Note:
> This e-mail and any attachments are confidential and the information herein
> is property of Quest Innovations B.V.. If you are not the intended recipient(s) of this e-mail,you are hereby notified that any dissemination, distribution, 
> copying, use of or reliance upon the information contained within this e-mail 
> or attachments is unauthorized and strictly prohibited. If you have received
> this e-mail in error, please notify us immediately by returning it to the
> sender and delete this copy from your system.
> 
> Quest Innovations B.V.

drop this silly BS on publically accessible, web-archived mailing
lists:) If it's added to any email sent out from your company, maybe
you'd ask to officially use something like a @gmx.net based email
address for kernel development; if you're intending to build a
proprietary driver, don't expect too much help...

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
   ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]