lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 7 Apr 2014 20:25:40 +0200
From:	L. Alberto Giménez <agimenez@...valve.es>
To:	Takashi Iwai <tiwai@...e.de>
Cc:	devel@...verdev.osuosl.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Chris Bajumpaa <cbajumpa@...il.com>,
	Arnd Bergmann <arnd@...db.de>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging/line6: Fix kzalloc coding style issue

On Mon, Apr Apr 2014 at 08:05:04AM +0200, Takashi Iwai said:
> At Mon,  7 Apr 2014 00:12:30 +0200,
> L. Alberto Giménez wrote:
> > 
> > Pass the actual variable to sizeof instead of a type definition.
> > 
> > Signed-off-by: L. Alberto Giménez <agimenez@...valve.es>
> 
> Acked-by: Takashi Iwai <tiwai@...e.de>
> 
> BTW, does anyone work on line6 stuff actively?
> It's been in staging forever, and it's difficult to promote to the
> standard ALSA driver unless testing with the real hardware by some
> motivated person...

I'm Not sure of that. I think that development has somewhat stalled. I
have line6 hardware that at the moment is not supported (HD500), and I
would like to take the shot. But the problem is that there are no specs,
and Line6 won't release any (I asked, several times, even offering to
accept some kind of stupid NDA). So I would need to reverse engineer
Windows drivers, and I don't have the knowledge to interpret captured
USB traffic, so I'm stuck as well.

I'll try to revive the line6-devel mailing list sending some traffic
captures and see if anyone can help or point me in the right direction.
I would like to see my HD500 running natively on Linux, and it's a nice
challenge to actually do some useful work for the kernel :)


Regards,
L. Alberto Giménez

P.S.: I sent this mail this morning from an alternative machine, and it
seems that the mail configuration was broken. Resending, sorry if you
received this message twice.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists