On Saturday 10 March 2007, Adam Kropelin wrote:
>Jiri Kosina wrote:
>> I am still however pretty far from being convinced that this will make
>> your application work. But as I absolutely don't know what your
>> application is expecting to obtain from serial port and how does this
>> compare to wha
On Saturday 10 March 2007, Jiri Kosina wrote:
>On Sat, 10 Mar 2007, Gene Heskett wrote:
>> >I think there is alternative for you that can be done completely in
>> >userland, without seeding mess into the kernel driver - do you think
>> > it would be feasible that you create a trivial and small libr
On Saturday 10 March 2007, Jiri Kosina wrote:
>On Sat, 10 Mar 2007, Gene Heskett wrote:
>> >So these broken programs think that while talking to hiddev device,
>> > they are in fact receiving data from serial port, right?
>>
>> I believe that to be the case, this code is very old and moldy.
>
>That
Jiri Kosina wrote:
> I am still however pretty far from being convinced that this will make
> your application work. But as I absolutely don't know what your
> application is expecting to obtain from serial port and how does this
> compare to what it is getting from usb hiddev, it's just wild guess
On Sat, 10 Mar 2007, Gene Heskett wrote:
> >I think there is alternative for you that can be done completely in
> >userland, without seeding mess into the kernel driver - do you think it
> >would be feasible that you create a trivial and small library, that
> I'm not up to writing a library. 15
On Sat, 10 Mar 2007, Gene Heskett wrote:
> >So these broken programs think that while talking to hiddev device, they
> >are in fact receiving data from serial port, right?
> I believe that to be the case, this code is very old and moldy.
That's quite sad. In fact, it would quite surprise me if th
On Saturday 10 March 2007, Jiri Kosina wrote:
>On Thu, 8 Mar 2007, Gene Heskett wrote:
>> I believe the problem to be that when their version of upsd is trying
>> to open the /dev/name its given, it is assuming and hard coded to do
>> the ioctl's to set the ports speed in baudrate, width of word, p
On Saturday 10 March 2007, Jiri Kosina wrote:
>On Fri, 9 Mar 2007, Gene Heskett wrote:
>> Oh? I wasn't aware of that. What other data paths can it use besides
>> a usb port?
>
>Until 2.6.20, HID in kernel was USB-only thing. In 2.6.20 I have
> distilled the generic HID layer, which is now also ho
On Fri, 9 Mar 2007, Gene Heskett wrote:
> Oh? I wasn't aware of that. What other data paths can it use besides a
> usb port?
Until 2.6.20, HID in kernel was USB-only thing. In 2.6.20 I have distilled
the generic HID layer, which is now also hooked by the Bluetooth code, as
there are many Blu
On Thu, 8 Mar 2007, Gene Heskett wrote:
> I believe the problem to be that when their version of upsd is trying to
> open the /dev/name its given, it is assuming and hard coded to do the
> ioctl's to set the ports speed in baudrate, width of word, parity etc.
Hi Gene,
first, sorry for replying
On Friday 09 March 2007, Adam Kropelin wrote:
>Gene Heskett wrote:
>> On Thursday 08 March 2007, Gene Heskett wrote:
>>> Greetings;
>>>
>>> Belkin is being non-responsive to requests for updated drivers for
>>> their line of UPS's, all of which now have a USB port which is the
>>> Belkin recommende
On Fri, 09 Mar 2007 19:28:24 -0500, Gene Heskett <[EMAIL PROTECTED]> wrote:
> > should. Try to resend to <[EMAIL PROTECTED]> and cc: to linux-kernel. HID
> > is not specific to USB.
> I did just now send a message to jiri, but it bounced at approximately C
> speed, plus or minus a few percent.
>
On Friday 09 March 2007, Adam Kropelin wrote:
>Gene Heskett wrote:
>> On Thursday 08 March 2007, Gene Heskett wrote:
>>> Greetings;
>>>
>>> Belkin is being non-responsive to requests for updated drivers for
>>> their line of UPS's, all of which now have a USB port which is the
>>> Belkin recommende
On Friday 09 March 2007, Pete Zaitcev wrote:
>On Fri, 09 Mar 2007 01:03:32 -0500, Gene Heskett
<[EMAIL PROTECTED]> wrote:
>> Its been about a day now, and no one has commented. Am I an idiot or
>> ??
>
>I think it means that Jiri Kosina is not on this list. I haven't got
>a clue if what you propo
Gene Heskett wrote:
> On Thursday 08 March 2007, Gene Heskett wrote:
>> Greetings;
>>
>> Belkin is being non-responsive to requests for updated drivers for
>> their line of UPS's, all of which now have a USB port which is the
>> Belkin recommended way to talk to these things.
>>
>> Unforch, the bel
On Fri, 09 Mar 2007 01:03:32 -0500, Gene Heskett <[EMAIL PROTECTED]> wrote:
> Its been about a day now, and no one has commented. Am I an idiot or ??
I think it means that Jiri Kosina is not on this list. I haven't got
a clue if what you propose is a good idea... Although in theory I should.
Try
On Thursday 08 March 2007, Gene Heskett wrote:
>Greetings;
>
>Belkin is being non-responsive to requests for updated drivers for their
>line of UPS's, all of which now have a USB port which is the Belkin
>recommended way to talk to these things.
>
>Unforch, the belkin supplied *nix stuff was last c
Greetings;
Belkin is being non-responsive to requests for updated drivers for their
line of UPS's, all of which now have a USB port which is the Belkin
recommended way to talk to these things.
Unforch, the belkin supplied *nix stuff was last compiled on an rh5.2
machine using gcc-2.7.2, so the
18 matches
Mail list logo
