mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Aarnio <matti.aarnio@zmailer.org>
To: abonilla <abonilla@linuxwireless.org>
Cc: Jesper Juhl <juhl-lkml@dif.dk>, linux-kernel@vger.kernel.org
Subject: Re: IBM Thinkpad T42 - Looking for a Developer.
Date: Fri, 15 Apr 2005 03:17:47 +0300	[thread overview]
Message-ID: <20050415001747.GO3858@mea-ext.zmailer.org> (raw)
In-Reply-To: <20050414223641.M49815@linuxwireless.org>

On Thu, Apr 14, 2005 at 06:40:16PM -0400, abonilla wrote:
> On Thu, 14 Apr 2005 23:20:19 +0200 (CEST), Jesper Juhl wrote
> > >  This is located in my home PC, Won't be the fastest downloads...
> > >  
> > >  http://wifitux.com/finger/
> > >  
> > Under what terms did you obtain these documents and from where? Are 
> > they completely freely distributable or are there strings attached?
> 
> I emailed the guys and they told me, "Hey, here you go, let me know if you
> want more information"

Those documents and files are downloadable also from   www.upek.com
They are rather scattered out there, but still...

In Linux environment we do need to define and implement our own
interface to the the device.  There is  BioAPI (www.bioapi.org)
interface specification, but that is rather high up in the application
stack.  (There exists also NIST written Linux version at that site,
and it seems to be "BSD with advertisement clause" licensed...)

My reading so far seems to indicate, that this is mostly doable
in the application space without needing kernel space drivers.

Implementing BioAPI interface library with device specific backends
(much in the same manner as SANE works) is the way, I do think.
To how large an extent the existing source code can be used
in this is so far unknown.

To be able to do the device specific backends, I do need to have
the detailed USB interface protocol descriptions, not just a windows
library binary wrapping them up into BioAPI.   I can handle NDA 
documents as long as the resulting source code into Linux (and any
other UNIX-like system capable to use it) can be published.

> > -- 
> > Jesper

/Matti Aarnio

  parent reply	other threads:[~2005-04-15  0:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14 21:10 Alejandro Bonilla
2005-04-14 21:20 ` Jesper Juhl
2005-04-14 22:40   ` abonilla
2005-04-14 23:15     ` Matti Aarnio
2005-04-14 23:54       ` Jeff Lessem
2005-04-15  3:20         ` Alejandro Bonilla
2005-04-15 10:09           ` Matti Aarnio
2005-04-15  0:12       ` Jesper Juhl
2005-04-15  0:17     ` Matti Aarnio [this message]
2005-04-16 22:05       ` Adam
  -- strict thread matches above, loose matches on Subject: below --
2005-04-14 20:52 Alejandro Bonilla
2005-04-14 21:06 ` Jesper Juhl

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=20050415001747.GO3858@mea-ext.zmailer.org \
    --to=matti.aarnio@zmailer.org \
    --cc=abonilla@linuxwireless.org \
    --cc=juhl-lkml@dif.dk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®