[INPUT] simple question on driver initialisation.

[INPUT] simple question on driver initialisation.

[moreau francis]

Hi,

I'm currently developping a very simple driver for a pinpad by using
Input module. I'm using Event handler to pass events from pinpad to userland.
In this simple case, I'm wondering if I really need to initialise
"phys" field in in "input_dev" struct before calling "input_register_device".
What is this field for ?

Thanks for your answers,

         Francis.


	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: [INPUT] simple question on driver initialisation.

[Vojtech Pavlik]

On Tue, Jul 26, 2005 at 12:23:40PM +0200, moreau francis wrote:

> I'm currently developping a very simple driver for a pinpad by using
> Input module. I'm using Event handler to pass events from pinpad to userland.
> In this simple case, I'm wondering if I really need to initialise
> "phys" field in in "input_dev" struct before calling "input_register_device".

Yes, it is required.

> What is this field for ?
 
It is intended for identifying the device based on "location" in the
system.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: [INPUT] simple question on driver initialisation.

[moreau francis]

hello,

--- Vojtech Pavlik <vojtech@suse.cz> a écrit :

> > What is this field for ?
>  
> It is intended for identifying the device based on "location" in the
> system.
> 

hmm, sorry but I don't understand you. I initialised this field with
"pinpad/input0" but the only place I can grep or find it, is in
/proc/bus/input/devices. I don't see how it can be used for identifiying
the device...

thanks for your time

          Francis


	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: [INPUT] simple question on driver initialisation.

[Vojtech Pavlik]

On Tue, Jul 26, 2005 at 01:47:05PM +0200, moreau francis wrote:
> hello,
> 
> --- Vojtech Pavlik <vojtech@suse.cz> a écrit :
> 
> > > What is this field for ?
> >  
> > It is intended for identifying the device based on "location" in the
> > system.
> > 
> 
> hmm, sorry but I don't understand you. I initialised this field with
> "pinpad/input0" but the only place I can grep or find it, is in
> /proc/bus/input/devices. I don't see how it can be used for identifiying
> the device...

It's also available via an ioctl() and in sysfs. This allows you to
specify in an application that you want a device plugged into a specific
port of the machine. Not many applications can use it at the moment, but
udev can use it to assign a name of the device node.

"pinpad/input0" doesn't sound right. What port is your pinpad connected
to?

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: [INPUT] simple question on driver initialisation.

[moreau francis]

Thanks Vojtech for your answers !

--- Vojtech Pavlik <vojtech@suse.cz> a écrit :

> It's also available via an ioctl() and in sysfs. This allows you to
> specify in an application that you want a device plugged into a specific
> port of the machine. Not many applications can use it at the moment, but
> udev can use it to assign a name of the device node.
> 

hmm, how can I use ioctl to find the location device since I need the location
to pass it to ioctl ?

I can't find "pinpad/input0" in sysfs, does that mean I need to add sysfs
suppport in my driver, and it's not done in input module when I register 
my input driver ?

> "pinpad/input0" doesn't sound right. What port is your pinpad connected
> to?
> 

Actually I'm working on an embedded system which owns a pinpad controller.
This controller is accessed by using io mem and it talks to the pinpad through
a dedicated bus. So I accessed it through io space.

thanks,

         Francis.


	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

Re: [INPUT] simple question on driver initialisation.

[Vojtech Pavlik]

On Tue, Jul 26, 2005 at 02:26:02PM +0200, moreau francis wrote:
> Thanks Vojtech for your answers !
> 
> --- Vojtech Pavlik <vojtech@suse.cz> a écrit :
> 
> > It's also available via an ioctl() and in sysfs. This allows you to
> > specify in an application that you want a device plugged into a specific
> > port of the machine. Not many applications can use it at the moment, but
> > udev can use it to assign a name of the device node.
> > 
> 
> hmm, how can I use ioctl to find the location device since I need the location
> to pass it to ioctl ?
> 
> I can't find "pinpad/input0" in sysfs, does that mean I need to add sysfs
> suppport in my driver, and it's not done in input module when I register 
> my input driver ?

I'm sorry, I thought it's already in mainline, but that bit is still
missing from the sysfs support in input. It'll get there soon.

> > "pinpad/input0" doesn't sound right. What port is your pinpad connected
> > to?
> 
> Actually I'm working on an embedded system which owns a pinpad controller.
> This controller is accessed by using io mem and it talks to the pinpad through
> a dedicated bus. So I accessed it through io space.

In that case, you'll likely want something like io0200/input0, where
0x200 would be the io address of the device. On the other hand, if it's
really embedded and there can't be two pinpads in the system, it's not a
problem to use basically any string there, since it only needs to be
system-unique.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

Re: [INPUT] simple question on driver initialisation.

[moreau francis]

--- Vojtech Pavlik <vojtech@suse.cz> a écrit :
> > 
> > I can't find "pinpad/input0" in sysfs, does that mean I need to add sysfs
> > suppport in my driver, and it's not done in input module when I register 
> > my input driver ?
> 
> I'm sorry, I thought it's already in mainline, but that bit is still
> missing from the sysfs support in input. It'll get there soon.
> 

cool.

> > > "pinpad/input0" doesn't sound right. What port is your pinpad connected
> > > to?
> > 
> > Actually I'm working on an embedded system which owns a pinpad controller.
> > This controller is accessed by using io mem and it talks to the pinpad
> through
> > a dedicated bus. So I accessed it through io space.
> 
> In that case, you'll likely want something like io0200/input0, where
> 0x200 would be the io address of the device. On the other hand, if it's
> really embedded and there can't be two pinpads in the system, it's not a
> problem to use basically any string there, since it only needs to be
> system-unique.
> 

It will be the case: only one embedded pinpad in the system. So something
like "kbdport/input0" should be ok...

thanks Vojtech for your time.

         Francis


	

	
		
___________________________________________________________________________ 
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger 
Téléchargez cette version sur http://fr.messenger.yahoo.com

TCP Network performance degade from 2.4.18 to 2.6.10

[Eshwar]

HI all,

I observed there is huge network performance drop from linux 2.4 to 2.6 with
the same setup (No hardware changes..). The results are taken in PIV
processor with D-Link network card... with iperf ... Can some body help me
why such a huge difference... in TCP stream... 

In linux 2.4 (Redhat 9)

DLink	
    TCP              UDP
Tx       94.3Mbps    Tx               95 Mbps
Rx       94.2 Mbps   Rx               95 Mbps

In linux 2.6.10 (Fedora Core 4)
DLink	
	 TCP                     UDP
Tx       64.3 Mbps 	Tx               87 Mbps
Rx       88.1 Mbps      Rx               95 Mbps


Thanks & Regards
Eshwar

Re: TCP Network performance degade from 2.4.18 to 2.6.10

[Stephen Hemminger]

On Wed, 28 Sep 2005 10:42:22 +0530
"Eshwar" <eshwar@moschip.com> wrote:

> HI all,
> 
> I observed there is huge network performance drop from linux 2.4 to 2.6 with
> the same setup (No hardware changes..). The results are taken in PIV
> processor with D-Link network card... with iperf ... Can some body help me
> why such a huge difference... in TCP stream... 
> 
> In linux 2.4 (Redhat 9)
> 
> DLink	
>     TCP              UDP
> Tx       94.3Mbps    Tx               95 Mbps
> Rx       94.2 Mbps   Rx               95 Mbps
> 
> In linux 2.6.10 (Fedora Core 4)
> DLink	
> 	 TCP                     UDP
> Tx       64.3 Mbps 	Tx               87 Mbps
> Rx       88.1 Mbps      Rx               95 Mbps
> 
> 
> Thanks & Regards
> Eshwar

Please send network performance discussion to netdev@vger.kernel.org

A lot more information is needed, like:
	* which hardware is on both ends of the test (lscpci)
	* any TCP configuration issues
	* any errors reported.
	* netfilter and firewalling.