From: "Keith A. Milner" <maillist@superlative.org>
To: alsa-devel@alsa-project.org
Cc: Jeffrey Scott Flesher Gmail <jeffrey.scott.flesher@gmail.com>
Subject: Re: GR-55 Driver
Date: Mon, 23 May 2011 17:01:58 +0100 [thread overview]
Message-ID: <201105231701.59052.maillist@superlative.org> (raw)
In-Reply-To: <1305839384.4443.41.camel@TrinaryDragon>
On Thursday 19 May 2011 22:09:44 Jeffrey Scott Flesher Gmail wrote:
> Please take a second look at this information:
>
> I do not see evidence that this driver patch is working as it should;
I'm tempted to agree from the info on the thread.
>
> Lets step back and look at this with Fresh eyes:
>
> This is the Roland GR-55 Guitar Synthesizer
> http://www.rolandus.com/products/productdetails.php?ProductId=1148
>
> You based this driver patch on the
>
> BOSS JS-8
> http://www.bossus.com/gear/productdetails.php?ProductId=1027
>
> Instead of the GT-10; which seems more similar, but I do not know
> anything about the difference in drivers, nor do I know that you have a
> working driver for the GT-10, or that its based on the JS-8.
I would say not. I "developed" (rather a grand term for the little I actually
did) the quirks for the JS-8 just recently.
I'm not sure where the GT-10 came from, but it's not derived from the JS-8.
In fact my memory on this is poor (and I had some pointers from this mailing
list) so the JS-8 may have been derived from the GT-10 at least in part,
rather than the other way around
So with this, and also with the benefit of knowing what the JS-8, GT-10 and
GR-55 are, I would agree the JS-8 probably isn't the right starting point for
this.
> As such, all I can do is go along and see if I can get this to work; so
> humor me, and lets see about basing this on the GT-10 and see how that
> works; from what I read; they might be based on the same chip set;
On the other hand, the quirk entries for GT-10 and JS-8 are very close to
being identical. I wonder if the GR-55 needs some specific .data like the GT-10
does. It may be worth taking the GT-10 entry and changing it for the GR-55
vid/pid and trying it.
Unfortunately, much as I would love a GR-55 to play with, I can't really
justify getting one to experiment with drivers on, otherwise I would love to
tinker with trying to get this going.
Cheers,
--
Keith A. Milner
next prev parent reply other threads:[~2011-05-23 16:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 18:20 GR-55 Driver Jeffrey Scott Flesher Gmail
2011-05-12 19:47 ` Daniel Mack
[not found] ` <1305233604.8214.2.camel@TrinaryDragon>
2011-05-13 0:16 ` Daniel Mack
[not found] ` <1305253856.5076.65.camel@TrinaryDragon>
2011-05-13 7:29 ` Daniel Mack
[not found] ` <BANLkTi=jj7cjxgmOpH+EHnUMuazqLOEsZA@mail.gmail.com>
2011-05-15 6:39 ` Jeffrey Scott Flesher Gmail
2011-05-15 11:36 ` Daniel Mack
2011-05-15 23:13 ` Jeffrey Scott Flesher Gmail
2011-05-16 7:05 ` Daniel Mack
2011-05-16 21:33 ` Jeffrey Scott Flesher Gmail
2011-05-17 10:11 ` Daniel Mack
2011-05-18 5:24 ` Jeffrey Scott Flesher Gmail
2011-05-18 15:34 ` Jeffrey Scott Flesher Gmail
2011-05-18 17:39 ` Daniel Mack
2011-05-19 21:09 ` Jeffrey Scott Flesher Gmail
2011-05-23 16:01 ` Keith A. Milner [this message]
2011-05-23 17:08 ` Daniel Mack
2011-05-24 13:30 ` Keith A. Milner
2011-05-24 18:28 ` Jeffrey Scott Flesher Gmail
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=201105231701.59052.maillist@superlative.org \
--to=maillist@superlative.org \
--cc=alsa-devel@alsa-project.org \
--cc=jeffrey.scott.flesher@gmail.com \
/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).