Re: NTSC Video on the 823

2 messages, 2 authors, 2001-03-23 · open the first message on its own page

Re: NTSC Video on the 823

From: <hidden>
Date: 2001-03-23 17:29:17

quoted
quoted
quoted
Where did you find these files?
ftp://ftp.mvista.com/pub/Area51/embedded-planet/video.tgz



Matthel Locke wrote:
quoted
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.

quoted
quoted
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/

Re: NTSC Video on the 823

From: Matthew Locke <hidden>
Date: 2001-03-23 18:30:52

"Todd_Tomaino"@vnci.net wrote:
quoted
quoted
quoted
quoted
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:
quoted
quoted
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.
quoted
quoted
quoted
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/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help