From: Matthew Locke <mlocke@mvista.com>
To: "Todd_Tomaino"@vnci.net
Cc: Dan Malek <dan@mvista.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: NTSC Video on the 823
Date: Fri, 23 Mar 2001 10:30:52 -0800 [thread overview]
Message-ID: <3ABB965C.796E2296@mvista.com> (raw)
In-Reply-To: 85256A18.005DD98E.00@ushq1.vnci.net
"Todd_Tomaino"@vnci.net wrote:
>
> >>>>Where did you find these files?
>
> ftp://ftp.mvista.com/pub/Area51/embedded-planet/video.tgz
oh yeah, I guess i put it there:-)
>
> Matthel Locke wrote:
> >>chuck's code is based on a different i2c driver than the one in
> >>8xx_io. Unless Todd has the i2c driver developed by EP, it probably
> >>won't work
>
> The "patchVideo" file contains an I2c driver. I did not load it, assuming
> that the more recent version I currently use would be preferable and
> compatible. I will try recompiling with the "patch Video" version and see
> if there is any change.
yep, that is the problem. the i2c driver in the kernel source doesn't
have write capablity. which is why the open (below) fails.
>
> >>>Where is this "Open error -19" coming from? There is lots more
> >>>code executed than your little snippet shows.
>
> It could be from this code segment located in Vid823.c, I'm not sure what
> this indicates.
>
> /* open or close a file in kernel space... */
> struct file *drvfopen(const char * filename, int flags, int mode)
> {
> struct file *f;
> int error;
>
> f = filp_open(filename, flags, mode);
> error = PTR_ERR(f);
> if (IS_ERR(f))
> {
> ========> printk("Open error %d\n",error);
> return 0;
> }
> return f;
>
> thanks for the help!
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-03-23 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 17:29 NTSC Video on the 823 Todd_Tomaino
2001-03-23 18:30 ` Matthew Locke [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-22 18:02 Todd M. Tomaino
2001-03-22 21:40 ` Dan Malek
2001-03-22 22:01 ` 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=3ABB965C.796E2296@mvista.com \
--to=mlocke@mvista.com \
--cc=Todd_Tomaino@vnci.net \
--cc=dan@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.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 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).