From: Dan Malek <dan@mvista.com>
To: "Todd M. Tomaino" <ttomaino@coe.neu.edu>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: NTSC Video on the 823
Date: Thu, 22 Mar 2001 16:40:01 -0500 [thread overview]
Message-ID: <3ABA7131.DADAE7BA@mvista.com> (raw)
In-Reply-To: Pine.SV4.4.10.10103221257340.26535-100000@Radians.coe.neu.edu
"Todd M. Tomaino" wrote:
> I followed the readme instructions for adding the VideoTest.c and Vid823.c
> files with the following header comments:
Where did you find these files?
> + * Started with Dan's LCD code, created NTSC Video Driver (4/2000)
> + * Chuck Spaur (chuck@spaur.com)
Although I wrote the first LCD driver, it has been fortunately discarded
and written as a proper frame buffer driver by others (at least Joe
Green). I have no idea what Chuck did to the original driver when
he created this one.
> made it to here !!!
> Open error -19
Where is this "Open error -19" coming from? There is lots more
code executed than your little snippet shows.
> void initVideo(IMAGEINFO *p_image)
> {
> int num_pages, i, j;
> u_char *fbuf, *cp;
> printf("made it to here !!!\n");
> =====>>>if ((p_image->display_fd = open("/dev/vid", O_RDWR)) < 0) {
> perror("video open");
> exit(2);
Either your open is actually successful and further in the program
there is some error, or the driver is failing in the open function
and printing that error above. It looks like some NULL pointer
dereference.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-22 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 18:02 NTSC Video on the 823 Todd M. Tomaino
2001-03-22 21:40 ` Dan Malek [this message]
2001-03-22 22:01 ` Matthew Locke
-- strict thread matches above, loose matches on Subject: below --
2001-03-23 17:29 Todd_Tomaino
2001-03-23 18:30 ` Matthew Locke
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=3ABA7131.DADAE7BA@mvista.com \
--to=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ttomaino@coe.neu.edu \
/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).