linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brian Magnuson" <bdmagnuson@gmail.com>
To: Jan Kratochvil <honza@jikos.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] new driver for wireless xbox receiver for review
Date: Wed, 30 May 2007 10:51:05 -0400	[thread overview]
Message-ID: <bafd4ab0705300751q67eb54efi1a46779576e0d202@mail.gmail.com> (raw)
In-Reply-To: <alpine.LRH.0.98.0705301614040.22353@twin.jikos.cz>

[-- Attachment #1: Type: text/plain, Size: 2008 bytes --]

Hi,

First off,  are there list archives for linux-input?  I wasn't able to find
any and
http://atrey.karlin.mff.cuni.cz/lab/listserv.html is a dead link.  Remaining
comments inline.

On 5/30/07, Jan Kratochvil <honza@jikos.cz> wrote:
>
> Hello,
>
> >> > Knew that was coming :).  Should be able to manage it.  Since the
> >> wireless
> >> > model returns a expanded data format it needs to be handled
> specially.
> >> > Another flag in the xpad_device struct?
> >>
> >> We have xtype field, I think it should be used.
> >
> >
> > I don't see this field in xpad_device in your tree or Linus'.
>
> It is not yet in Linus' tree, but it definitely is in Dmitry input tree.
>
> http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=bad058541d848500b5f2cc049c1082d0b2935b7d


Indeed it is.  I think this is just some basic git ignorance on my part.  I
clearly see it in
the link you provided but if I descend from the tree link starting from top
commit at
http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=summary I get
some older
version of xpad.c.  Am I just being dense (likely) or is there something
wrong?

I noticed in your patch that you worked on some old version of xpad. You'll
> see that in dmitry tree there is support for rumble as well as other minor
> changes. (And I submited support for controlling leds yesterday)
> Btw you are stating that it process packet is based on information from
> http://euc.jp/periphs/xbox-controller.en.html, which I doubt, because this
> page
> is actually about xbox (1) controller. Not xbox 360. But on the other hand
> you
> are interpreting the report correctly. :)


Turns out I started developing from a version of xpad.c  distributed with
Ubuntu which
1) is old and 2) appears to contain some extra patches on top of that.  That
link you
refer to is a a stale comment. I'll remove it.

>
> > In any case I'll take these changes and your earlier ones, merge it into
> > xpad.c and
> > resubmit.
>
> Good luck,
> Jan


Thanks :)

-Brian

[-- Attachment #2: Type: text/html, Size: 3153 bytes --]

  reply	other threads:[~2007-05-30 14:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29  4:39 [PATCH] new driver for wireless xbox receiver for review Brian Magnuson
2007-05-29 15:59 ` Dmitry Torokhov
2007-05-30  0:28   ` Brian Magnuson
2007-05-30 12:40     ` Dmitry Torokhov
2007-05-30 13:47       ` Brian Magnuson
2007-05-30 14:24         ` Jan Kratochvil
2007-05-30 14:51           ` Brian Magnuson [this message]
2007-05-30 15:02             ` Dmitry Torokhov
2007-05-30 15:31               ` Brian Magnuson
2007-05-30  9:51 ` Jiri Kosina

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=bafd4ab0705300751q67eb54efi1a46779576e0d202@mail.gmail.com \
    --to=bdmagnuson@gmail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=honza@jikos.cz \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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;
as well as URLs for NNTP newsgroup(s).