linuxconsole-dev

inputattach on sa1100

[Justin C. <jp...@do...>]

Trying to get the input drivers working on Arm (sa1100), and having
problems with inputattach. First is that it isnt dropping RTS to reset
the devices. Someone else is working on that - it doesnt matter for all
devices anyway. However I am getting a failure in

        devt = SERIO_RS232 | input_types[type].type | (input_types[type].extra << 16);

        if(ioctl(fd, SPIOCSTYPE, &devt)) {
                fprintf(stderr, "inputattach: can't set device type\n");
                return 1;
        }

basically the ioctl seems to fail, which is from serport.c:

static int serport_ldisc_ioctl(struct tty_struct * tty, struct file * file, unsigned int cmd, unsigned long arg)
{
        struct serport *serport = (struct serport*) tty->disc_data;
        
        switch (cmd) {
                case SPIOCSTYPE:
                        return get_user(serport->serio.type, (unsigned long *) arg);
        }

        return -EINVAL;
}

Any idea whats wrong here? The cast looks a little odd to me. But I dont really
know my way around this code very well yet...

Justin

Re: inputattach on sa1100

[James S. <jsi...@su...>]

On Tue, 16 Jan 2001, Justin Cormack wrote:

> Trying to get the input drivers working on Arm (sa1100), and having
> problems with inputattach. 

Arm :-) How does ruby work on it?

> First is that it isnt dropping RTS to reset
> the devices. Someone else is working on that - it doesnt matter for all
> devices anyway. 

Could the patch been sent are way once you are done?

> However I am getting a failure in
> 
>         devt = SERIO_RS232 | input_types[type].type | (input_types[type].extra << 16);
> 
>         if(ioctl(fd, SPIOCSTYPE, &devt)) {
>                 fprintf(stderr, "inputattach: can't set device type\n");
>                 return 1;
>         }

What is the exact error you are getting? What serial device are you using?
Are they modular or built in?
 

Re: inputattach on sa1100

[Justin C. <jp...@do...>]

> 
> 
> On Tue, 16 Jan 2001, Justin Cormack wrote:
> 
> > Trying to get the input drivers working on Arm (sa1100), and having
> > problems with inputattach. 
> 
> Arm :-) How does ruby work on it?

Sorry, doesnt. Yet. These are the standard kernel js drivers, but they are
the same as the ruby ones. There are several input drivers (touchscreen etc)
to convert to tuby plus the framebuffer code - will work on it gradually.

> > First is that it isnt dropping RTS to reset
> > the devices. Someone else is working on that - it doesnt matter for all
> > devices anyway. 
> 
> Could the patch been sent are way once you are done?

oh yes.

> > However I am getting a failure in
> > 
> >         devt = SERIO_RS232 | input_types[type].type | (input_types[type].extra << 16);
> > 
> >         if(ioctl(fd, SPIOCSTYPE, &devt)) {
> >                 fprintf(stderr, "inputattach: can't set device type\n");
> >                 return 1;
> >         }
> 
> What is the exact error you are getting? What serial device are you using?
> Are they modular or built in?

modular. spaceorb or newtonkbd. I'll do more debugging today and find out whats
going on exactly.

Justin

Re: inputattach on sa1100

[James S. <jsi...@su...>]

> > Arm :-) How does ruby work on it?
> 
> Sorry, doesnt. Yet. :-(

 These are the standard kernel js drivers, but they are
> the same as the ruby ones. There are several input drivers (touchscreen etc)
> to convert to tuby plus the framebuffer code - will work on it gradually.

Okay. We already have one touch screen driver (Gunze AHL-51S) to use as a
example. The framebuffer code needs alot of work.

> > Could the patch been sent are way once you are done?
> 
> oh yes.

Thanks.

> > What is the exact error you are getting? What serial device are you using?
> > Are they modular or built in?
> 
> modular. spaceorb or newtonkbd. I'll do more debugging today and find out whats
> going on exactly.

I only have a serial mouse which worked fine. All my joysticks are USB
and regular joystick port based. I do have a few commodore 64 and atari
josyticks but those only work if you plug them into the parallel port,
with a special adapter. Vojtech do you have a serial port based joysticks?

Re: inputattach on sa1100

[Justin C. <jp...@do...>]

> Okay. We already have one touch screen driver (Gunze AHL-51S) to use as a
> example. The framebuffer code needs alot of work.

I might do the touchscreen next - its quite simple I think.


> > > What is the exact error you are getting? What serial device are you using?
> > > Are they modular or built in?
> > 
> > modular. spaceorb or newtonkbd. I'll do more debugging today and find out whats
> > going on exactly.
> 
> I only have a serial mouse which worked fine. All my joysticks are USB
> and regular joystick port based. I do have a few commodore 64 and atari
> josyticks but those only work if you plug them into the parallel port,
> with a special adapter. Vojtech do you have a serial port based joysticks?

I fixed it. It was mostly my stupidity and modules misconfigured...

Justin

Re: inputattach on sa1100

[James S. <jsi...@su...>]

> > Okay. We already have one touch screen driver (Gunze AHL-51S) to use as a
> > example. The framebuffer code needs alot of work.
> 
> I might do the touchscreen next - its quite simple I think.

Cool :-)

> I fixed it. It was mostly my stupidity and modules misconfigured...

What did you so maybe it can be put into a FAQ ?