[RFC] re-queuing usx2y-fw

[RFC] re-queuing usx2y-fw

[Martin Langer]

Hi,

long time ago there was a thread about replacing tascam_loader.ihx with 
an open firmware:

http://sourceforge.net/mailarchive/message.php?msg_id=8555003

http://www.langerland.de/audio/usx2y/usx2y-fw-0.1b.tar.bz2

All results were quite positive and I've had a lot of downloads since 
them on my site and I never ever got a bugreport about it :)

What about a second attempt of merging it into alsa-firmware? Any new 
strategies for this step? The code still depends on as31 (8031/8051 
crosss-assembler) which still isn't available as .rpm or .deb, at least 
newer versions since 2.1. Should we care about it?

I use it on my US-122 since several months without problems and we have 
positive results from us224 and us428 owners. Even the size has only 20 
percent of the size of the original tascam file. Aren't these good 
reasons for deleting the original closed source file?

Another point is the license note in the README file for those Tascam 
files. Is it really true for tascam_loader.ihx? I (we?) know that 
tascam_loader.ihx and MidiSportLoader.ihx (for M-Audio MidiSport's) are 
100% identical; there's no difference. So I believe that this file is 
part of the same 3rd party development kit and is not be copyrighted by 
Tascam? I don't know it, but Tascam should know it better... just my 
two cents.


bye,
martin

 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [RFC] re-queuing usx2y-fw

[Takashi Iwai]

At Mon, 28 Mar 2005 17:51:51 +0200,
Martin Langer wrote:
> 
> Hi,
> 
> long time ago there was a thread about replacing tascam_loader.ihx with 
> an open firmware:
> 
> http://sourceforge.net/mailarchive/message.php?msg_id=8555003
> 
> http://www.langerland.de/audio/usx2y/usx2y-fw-0.1b.tar.bz2
> 
> All results were quite positive and I've had a lot of downloads since 
> them on my site and I never ever got a bugreport about it :)
> 
> What about a second attempt of merging it into alsa-firmware? Any new 
> strategies for this step?

No, I prefer the traditional one:  Send a patch :)

> The code still depends on as31 (8031/8051 
> crosss-assembler) which still isn't available as .rpm or .deb, at least 
> newer versions since 2.1. Should we care about it?

For convenience, we may include both the firmware source and binary in
the CVS repository, so that one can install even without as31.

> I use it on my US-122 since several months without problems and we have 
> positive results from us224 and us428 owners. Even the size has only 20 
> percent of the size of the original tascam file. Aren't these good 
> reasons for deleting the original closed source file?

Open-source version is _always_ good (if it provides the same
functionality).


> Another point is the license note in the README file for those Tascam 
> files. Is it really true for tascam_loader.ihx? I (we?) know that 
> tascam_loader.ihx and MidiSportLoader.ihx (for M-Audio MidiSport's) are 
> 100% identical; there's no difference. So I believe that this file is 
> part of the same 3rd party development kit and is not be copyrighted by 
> Tascam? I don't know it, but Tascam should know it better... just my 
> two cents.

If so, most likely you're right...


Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [RFC] re-queuing usx2y-fw

[Martin Langer]

On Tue, Mar 29, 2005 at 05:01:55PM +0200, Takashi Iwai wrote:
> At Mon, 28 Mar 2005 17:51:51 +0200,
> Martin Langer wrote:
> > 
> > What about a second attempt of merging it into alsa-firmware? Any new 
> > strategies for this step?
> 
> No, I prefer the traditional one:  Send a patch :)

Ok. Do we have any CodingStyle for assembler files? FreeStyle?

> > The code still depends on as31 (8031/8051 
> > crosss-assembler) which still isn't available as .rpm or .deb, at least 
> > newer versions since 2.1. Should we care about it?
> 
> For convenience, we may include both the firmware source and binary in
> the CVS repository, so that one can install even without as31.

Yep. I will try to introduce a new configure option like 
'--enable-buildfw' for it, or any similar solution.

> > I use it on my US-122 since several months without problems and we have 
> > positive results from us224 and us428 owners. Even the size has only 20 
> > percent of the size of the original tascam file. Aren't these good 
> > reasons for deleting the original closed source file?
> 
> Open-source version is _always_ good (if it provides the same
> functionality).

Full ACK. And it does provide the same functionality here (loading the 
main fw).


martin


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [RFC] re-queuing usx2y-fw

[Takashi Iwai]

At Tue, 29 Mar 2005 18:58:16 +0200,
Martin Langer wrote:
> 
> On Tue, Mar 29, 2005 at 05:01:55PM +0200, Takashi Iwai wrote:
> > At Mon, 28 Mar 2005 17:51:51 +0200,
> > Martin Langer wrote:
> > > 
> > > What about a second attempt of merging it into alsa-firmware? Any new 
> > > strategies for this step?
> > 
> > No, I prefer the traditional one:  Send a patch :)
> 
> Ok. Do we have any CodingStyle for assembler files? FreeStyle?

AFAIK, nothing special.  We have no strict limitation except for
kernel drivers which should follow the standard coding style.

> > > The code still depends on as31 (8031/8051 
> > > crosss-assembler) which still isn't available as .rpm or .deb, at least 
> > > newer versions since 2.1. Should we care about it?
> > 
> > For convenience, we may include both the firmware source and binary in
> > the CVS repository, so that one can install even without as31.
> 
> Yep. I will try to introduce a new configure option like 
> '--enable-buildfw' for it, or any similar solution.

That'll be nice.


thanks,

Takashi


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: [RFC] re-queuing usx2y-fw

[Martin Langer]

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

On Tue, Mar 29, 2005 at 07:03:12PM +0200, Takashi Iwai wrote:
> At Tue, 29 Mar 2005 18:58:16 +0200,
> Martin Langer wrote:
> > 
> > On Tue, Mar 29, 2005 at 05:01:55PM +0200, Takashi Iwai wrote:
> > > At Mon, 28 Mar 2005 17:51:51 +0200,
> > > Martin Langer wrote:
> > > > 
> > > > The code still depends on as31 (8031/8051 
> > > > crosss-assembler) which still isn't available as .rpm or .deb, at least 
> > > > newer versions since 2.1. Should we care about it?
> > > 
> > > For convenience, we may include both the firmware source and binary in
> > > the CVS repository, so that one can install even without as31.
> > 
> > Yep. I will try to introduce a new configure option like 
> > '--enable-buildfw' for it, or any similar solution.
> 
> That'll be nice.

Here it is. The new configure option for alsa-firmware is called 
'--enable-buildfw'. If you want to build it from source you have to 
install one of the latest versions of as31, which you can find at

http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31

(e.g. version 2.3.0 is fine)


martin

[-- Attachment #2: usx2y-fw.patch --]
[-- Type: text/plain, Size: 9136 bytes --]

--- ../alsa-firmware-1.0.8rc2/configure.in	2005-01-05 07:59:26.000000000 +0100
+++ configure.in	2005-03-31 12:18:12.186771056 +0200
@@ -13,9 +13,21 @@
 AC_ARG_ENABLE(hotplug,
   [  --disable-hotplug       Disable the hotplug fw loader support],
   [hotplug="$enableval"],[hotplug=yes])
+AC_ARG_ENABLE(buildfw,
+  [  --enable-buildfw        Enable building fw from source files],
+  [buildfw="$enableval"],[buildfw=no])
+
+AC_PATH_PROGS(AS31, as31)
+AS31_FLAGS="-Fhex"
+AC_SUBST(AS31_FLAGS)
+
+if test x"${AS31}" = x"";  then
+  buildfw=false
+fi
 
 AM_CONDITIONAL(USE_LOADER, test "$loader" = "yes")
 AM_CONDITIONAL(USE_HOTPLUG, test "$hotplug" = "yes")
+AM_CONDITIONAL(BUILD_FW, test "$buildfw" = "yes")
 
 AC_ARG_WITH(hotplug-dir,
   [  --with-hotplug-dir      Specify the hotplug firmware directory],
--- ../alsa-firmware-1.0.8rc2/usx2yloader/Makefile.am	2004-02-17 16:27:54.000000000 +0100
+++ usx2yloader/Makefile.am	2005-03-31 10:56:00.138556352 +0200
@@ -6,7 +6,15 @@
 		tascam_loader.ihx \
 		us122fw.ihx us224fw.ihx us428fw.ihx
 
-EXTRA_DIST = $(cfg_files)
+if BUILD_FW
+bin_SCRIPTS = tascam_loader
+tascam_loader: 
+	$(AS31) $(AS31_FLAGS) -s tascam_loader.asm > tascam_loader.ihx
+endif
+
+EXTRA_DIST = $(cfg_files) \
+	tascam_loader.asm \
+	an2131.asm
 
 firmwaredir = $(datadir)/alsa/firmware/$(MYNAME)
 firmware_DATA = $(cfg_files)
--- /dev/null	2005-03-31 12:13:37.935382568 +0200
+++ usx2yloader/an2131.asm	2004-06-10 21:57:32.000000000 +0200
@@ -0,0 +1,88 @@
+;
+;   Declaration of AN2131xx EZ-USB Registers
+;
+;
+;   Copyright (c) 2004	Martin Langer <martin-langer@gmx.de>
+;
+;
+;   This program is free software; you can redistribute it and/or
+;   modify it under the terms of the GNU General Public License
+;   as published by the Free Software Foundation; either version 2
+;   of the License, or any later version.
+;
+;   This program is distributed in the hope that it will be useful,
+;   but WITHOUT ANY WARRANTY; without even the implied warranty of
+;   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+;   GNU General Public License for more details.
+;
+;   You should have received a copy of the GNU General Public License
+;   along with this program; if not, write to the Free Software
+;   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+;
+;
+
+
+.equ DPL1,	0x84
+.equ DPH1,	0x85
+.equ DPS,	0x86		
+.equ CKCON,	0x8E
+.equ SPC_FNC,	0x8F
+.equ EXIF,	0x91
+.equ MPAGE,	0x92
+.equ SCON0,	0x98
+.equ SBUF0,	0x99
+.equ SCON1,	0xC0
+.equ SBUF1,	0xC1
+.equ EICON,	0xD8
+.equ EIE,	0xE8		; Interrupt Enables
+.equ EIP,	0xF8
+
+
+.equ OUT1BUF,	0x7E40
+.equ IN1BUF,	0x7E80
+.equ OUT0BUF,	0x7EC0
+.equ IN0BUF,	0x7F00
+.equ CPUCS,     0x7F92	
+.equ PORTACFG, 	0x7F93
+.equ PORTBCFG, 	0x7F94
+.equ PORTCCFG, 	0x7F95
+.equ OUTA,     	0x7F96	
+.equ OUTB,     	0x7F97
+.equ OUTC,     	0x7F98
+.equ PINSA,    	0x7F99
+.equ PINSB,    	0x7F9A
+.equ PINSC,    	0x7F9B
+.equ OEA,      	0x7F9C
+.equ OEB,      	0x7F9D
+.equ OEC,      	0x7F9E
+
+.equ I2CS,	0x7FA5		; I2C Control and Status
+.equ I2DAT,	0x7FA6		; I2C Data
+
+.equ IN07IRQ,	0x7FA9		; EP IN Interrupt Request
+.equ OUT07IRQ,	0x7FAA		; EP OUT Interrupt Request
+.equ USBIRQ,	0x7FAB		; USB Interrupt Request
+.equ USBIEN,	0x7FAE		; USB Interrupt Enables
+.equ USBBAV,	0x7FAF		; Breakpoint and Autovector
+.equ EP0CS,	0x7FB4		; Control and Status
+.equ IN0BC,	0x7FB5		; Byte Count
+.equ IN1CS,	0x7FB6
+.equ IN1BC,	0x7FB7
+.equ OUT0BC,	0x7FC5		; Byte Count
+.equ OUT1CS,	0x7FC6
+.equ OUT1BC,	0x7FC7
+.equ USBCS,	0x7FD6		; USB Control and Status
+.equ SD_BMREQ,	0x7FE8		; Setup Data Byte 1: bmRequest 
+					; c0: Vendor Request 'In'
+					; 40: Vendor Request 'Out'
+.equ SD_BREQ,	0x7FE9		; Setup Data Byte 2: bRequest
+					; a0: Internal Firmware Load
+					; a3: External Firmware Load ?
+.equ SD_VALL,	0x7FEA		; Setup Data Byte 3: Starting address (lo)
+.equ SD_VALH,	0x7FEB		; Setup Data Byte 4: Starting address (hi)
+.equ SD_INDL,	0x7FEC		; Setup Data Byte 5: 0x00
+.equ SD_INDH,	0x7FED		; Setup Data Byte 6: 0x00
+.equ SD_LENL,	0x7FEE		; Setup Data Byte 7: Number of Bytes (lo)
+.equ SD_LENH,	0x7FEF		; Setup Data Byte 8: Number of Bytes (hi)
+
+;;
--- /dev/null	2005-03-31 12:13:37.935382568 +0200
+++ usx2yloader/tascam_loader.asm	2005-03-31 13:31:32.765781360 +0200
@@ -0,0 +1,266 @@
+;
+;   Second stage AN2131QC (aka EzUSB) loader
+;
+;	
+;   Copyright (c) 2004-2005 Martin Langer <martin-langer@gmx.de>
+;
+;   Written for Tascam US-122/US-224/US-428 audio/MIDI devices
+;
+;   This program is free software; you can redistribute it and/or
+;   modify it under the terms of the GNU General Public License
+;   as published by the Free Software Foundation; either version 2
+;   of the License, or any later version.
+;
+;   This program is distributed in the hope that it will be useful,
+;   but WITHOUT ANY WARRANTY; without even the implied warranty of
+;   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+;   GNU General Public License for more details.
+;
+;   You should have received a copy of the GNU General Public License
+;   along with this program; if not, write to the Free Software
+;   Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
+;
+;
+
+.inc	"an2131.asm"
+
+
+; ====================================================== interrupt vectors ===
+
+	.org	0x0000			; reset vector
+	ljmp    init
+
+	.org	0x0043			; int2 vector (USB)
+	ljmp	usb_jump_table		; autovector will replace byte 45
+
+
+; =================================================================== init ===
+
+init:
+	mov	sp, #20h		; move stack pointer to 0x20
+
+	mov	a, EIE
+	setb	acc.0			; enable int2 (USB Interrupt)
+	mov	EIE, a
+	
+	mov	dptr, #USBIRQ
+	mov	a, #00011111b
+	movx	@dptr, a		; clear Interrupt Request
+
+	mov	dptr, #IN07IRQ
+	mov	a, #11111111b
+	movx	@dptr, a		; clear EP IN Interrupt Request
+
+	mov	dptr, #OUT07IRQ
+	mov	a, #11111111b
+	movx	@dptr, a		; clear EP OUT Interrupt Request
+
+	mov	dptr, #PORTCCFG
+	movx	a, @dptr
+	orl	a, #11000000b		; allow read and write on Port C
+	movx	@dptr, a
+
+	mov	dptr, #USBBAV
+	movx	a, @dptr
+	orl	a, #00000001b		; enable Autovector feature
+	movx	@dptr, a
+
+	mov	dptr, #USBIEN
+	movx	a, @dptr
+	orl	a, #00000101b		; enable 'Setup Data Available
+	movx    @dptr, a		; Interrupt Request' and 'Setup Token
+					; Interrupt Request'
+
+	setb	ea			; enable global 8051 Interrupts
+
+loop:
+	sjmp	loop
+
+
+; ========================================= usb interrupt service routines ===
+
+usb_jump_table:
+	ljmp	setup_data_avail_isr	; setup data available 
+	.db	0		
+	ljmp	start_of_frame_isr	; Start of frame
+	.db	0
+	ljmp	setup_token_isr		; loading setup data
+	.db	0
+	ljmp	usb_suspend_isr		; USB suspend
+	.db	0
+	ljmp	usb_reset_isr		; USB reset
+	.db	0
+	ljmp	spare_isr
+	.db	0
+	ljmp	ep0_in_isr
+	.db	0
+	ljmp	ep0_out_isr
+	.db	0
+	ljmp	ep1_in_isr
+	.db	0
+	ljmp	ep1_out_isr
+	.db	0
+	ljmp	ep2_in_isr
+	.db	0
+	ljmp	ep2_out_isr
+	.db	0
+	ljmp	ep3_in_isr
+	.db	0
+	ljmp	ep3_out_isr
+	.db	0
+	ljmp	ep4_in_isr
+	.db	0
+	ljmp	ep4_out_isr
+	.db	0
+	ljmp	ep5_in_isr
+	.db	0
+	ljmp	ep5_out_isr
+	.db	0
+	ljmp	ep6_in_isr
+	.db	0
+	ljmp	ep6_out_isr
+	.db	0
+	ljmp	ep7_in_isr
+	.db	0
+	ljmp	ep7_out_isr
+	.db	0
+
+setup_data_avail_isr:
+	push	acc
+	push	dph
+	push	dpl
+	push	dph1
+	push	dpl1
+	push	dps
+	mov	a, EXIF
+	clr	acc.4			; clear USB Interrupt Request
+	mov	EXIF, a
+	mov	dptr, #USBIRQ
+	mov	a, #00000001b		; Setup Data Avail. Interrupt Request
+	movx	@dptr, a
+	pop	dps
+	pop	dpl1
+	pop	dph1
+	pop	dpl
+	pop	dph
+	pop	acc
+	reti
+
+start_of_frame_isr:
+	push	acc
+	push	dph
+	push	dpl
+	push	dph1
+	push	dpl1
+	push	dps
+	mov	a, EXIF
+	clr	acc.4			; clear USB Interrupt Request
+	mov	EXIF, a
+	mov	dptr, #USBIRQ
+	mov	a, #00000010b		; Start of frame Interrupt Request
+	movx	@dptr, a
+	pop	dps
+	pop	dpl1
+	pop	dph1
+	pop	dpl
+	pop	dph
+	pop	acc
+	reti
+
+setup_token_isr:
+	push	acc
+	push	dph
+	push	dpl
+	push	dph1
+	push	dpl1
+	push	dps
+	mov	a, EXIF
+	clr	acc.4			; clear USB Interrupt Request
+	mov	EXIF, a
+	mov	dptr, #USBIRQ
+	mov	a, #00000100b		; Setup Token Interrupt Request
+	movx	@dptr, a
+	pop	dps
+	pop	dpl1
+	pop	dph1
+	pop	dpl
+	pop	dph
+	pop	acc
+	reti
+
+usb_suspend_isr:
+	push	acc
+	push	dph
+	push	dpl
+	push	dph1
+	push	dpl1
+	push	dps
+	mov	a, EXIF
+	clr	acc.4			; clear USB Interrupt Request
+	mov	EXIF, a
+	mov	dptr, #USBIRQ
+	mov	a, #00001000b		; USB Suspend Interrupt Request
+	movx	@dptr, a
+	pop	dps
+	pop	dpl1
+	pop	dph1
+	pop	dpl
+	pop	dph
+	pop	acc
+	reti
+
+usb_reset_isr:
+	push	acc
+	push	dph
+	push	dpl
+	push	dph1
+	push	dpl1
+	push	dps
+	mov	a, EXIF
+	clr	acc.4			; clear USB Interrupt Request
+	mov	EXIF, a
+	mov	dptr, #USBIRQ
+	mov	a, #00010000b		; USB Reset Interrupt Request
+	movx	@dptr, a
+	pop	dps
+	pop	dpl1
+	pop	dph1
+	pop	dpl
+	pop	dph
+	pop	acc
+	reti
+	
+spare_isr:
+	reti
+ep0_in_isr:
+	reti
+ep0_out_isr:
+	reti
+ep1_in_isr:
+	reti
+ep1_out_isr:
+	reti
+ep2_in_isr:
+	reti
+ep2_out_isr:
+	reti
+ep3_in_isr:
+	reti
+ep3_out_isr:
+	reti
+ep4_in_isr:
+	reti
+ep4_out_isr:
+	reti
+ep5_in_isr:
+	reti
+ep5_out_isr:
+	reti
+ep6_in_isr:
+	reti
+ep6_out_isr:
+	reti
+ep7_in_isr:
+	reti
+ep7_out_isr:
+	reti

Re: [RFC] re-queuing usx2y-fw

[Takashi Iwai]

At Thu, 31 Mar 2005 13:58:48 +0200,
Martin Langer wrote:
> 
> On Tue, Mar 29, 2005 at 07:03:12PM +0200, Takashi Iwai wrote:
> > At Tue, 29 Mar 2005 18:58:16 +0200,
> > Martin Langer wrote:
> > > 
> > > On Tue, Mar 29, 2005 at 05:01:55PM +0200, Takashi Iwai wrote:
> > > > At Mon, 28 Mar 2005 17:51:51 +0200,
> > > > Martin Langer wrote:
> > > > > 
> > > > > The code still depends on as31 (8031/8051 
> > > > > crosss-assembler) which still isn't available as .rpm or .deb, at least 
> > > > > newer versions since 2.1. Should we care about it?
> > > > 
> > > > For convenience, we may include both the firmware source and binary in
> > > > the CVS repository, so that one can install even without as31.
> > > 
> > > Yep. I will try to introduce a new configure option like 
> > > '--enable-buildfw' for it, or any similar solution.
> > 
> > That'll be nice.
> 
> Here it is. The new configure option for alsa-firmware is called 
> '--enable-buildfw'. If you want to build it from source you have to 
> install one of the latest versions of as31, which you can find at
> 
> http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> 
> (e.g. version 2.3.0 is fine)

Thanks, I added it to CVS now.

Could you prepare some document about as31?
Just mention the above in README of usx2yloader would suffice.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

Re: [RFC] re-queuing usx2y-fw

[Martin Langer]

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

On Thu, Mar 31, 2005 at 05:48:27PM +0200, Takashi Iwai wrote:
> At Thu, 31 Mar 2005 13:58:48 +0200,
> Martin Langer wrote:
> > On Tue, Mar 29, 2005 at 07:03:12PM +0200, Takashi Iwai wrote:
> > > At Tue, 29 Mar 2005 18:58:16 +0200,
> > > Martin Langer wrote:
> > > > On Tue, Mar 29, 2005 at 05:01:55PM +0200, Takashi Iwai wrote:
> > > > > At Mon, 28 Mar 2005 17:51:51 +0200,
> > > > > Martin Langer wrote:
> > > > > > 
> > > > > > The code still depends on as31 (8031/8051 
> > > > > > crosss-assembler) which still isn't available as .rpm or .deb, at least 
> > > > > > newer versions since 2.1. Should we care about it?
> > > > > 
> > > > > For convenience, we may include both the firmware source and binary in
> > > > > the CVS repository, so that one can install even without as31.
> > > > 
> > > > Yep. I will try to introduce a new configure option like 
> > > > '--enable-buildfw' for it, or any similar solution.
> > > 
> > > That'll be nice.
> > 
> > Here it is. The new configure option for alsa-firmware is called 
> > '--enable-buildfw'. If you want to build it from source you have to 
> > install one of the latest versions of as31, which you can find at
> > 
> > http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> > 
> > (e.g. version 2.3.0 is fine)
> 
> Thanks, I added it to CVS now.
> 
> Could you prepare some document about as31?
> Just mention the above in README of usx2yloader would suffice.

Of course, also including a small GPL copyright note.

martin

Summary: text added for building usx2y-fw from source file
Signed-off-by: Martin Langer <martin-langer@gmx.de>

[-- Attachment #2: readme.patch --]
[-- Type: text/plain, Size: 1081 bytes --]

Index: README
===================================================================
RCS file: /cvsroot/alsa/alsa-firmware/usx2yloader/README,v
retrieving revision 1.2
diff -u -r1.2 README
--- README	8 Apr 2004 16:48:46 -0000	1.2
+++ README	1 Apr 2005 10:15:13 -0000
@@ -5,8 +5,26 @@
 utility in alsa-tools package.  Install this with the same prefix
 option as you used for alsa-tools.
 
+BUILDING FIRMWARE FROM SOURCE
+=============================
+
+Building the firmware from source is possible, if you use the 
+configure option --enable-buildfw. Also, it requires the 8031/8051
+cross-assembler as31. As31 version 2.3.0 is fine for this job, but 
+every version since 2.2 should do it.
+
+As31 is available from:
+http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
+
+At the moment it's only possible to build tascam_loader.ihx from 
+source.
+
 COPYRIGHT
 =========
 
+tascam_loader.ihx, tascam_loader.asm and an2131.asm:
+Available under GPL without restrictions.
+
+other firmware files:
 Copyright (c) 2003 Tascam / TEAC Corporation.
 Distributable under GPL.

Re: [RFC] re-queuing usx2y-fw

[Takashi Iwai]

At Fri, 1 Apr 2005 12:26:12 +0200,
Martin Langer wrote:
> 
> On Thu, Mar 31, 2005 at 05:48:27PM +0200, Takashi Iwai wrote:
> > At Thu, 31 Mar 2005 13:58:48 +0200,
> > Martin Langer wrote:
> > > On Tue, Mar 29, 2005 at 07:03:12PM +0200, Takashi Iwai wrote:
> > > > At Tue, 29 Mar 2005 18:58:16 +0200,
> > > > Martin Langer wrote:
> > > > > On Tue, Mar 29, 2005 at 05:01:55PM +0200, Takashi Iwai wrote:
> > > > > > At Mon, 28 Mar 2005 17:51:51 +0200,
> > > > > > Martin Langer wrote:
> > > > > > > 
> > > > > > > The code still depends on as31 (8031/8051 
> > > > > > > crosss-assembler) which still isn't available as .rpm or .deb, at least 
> > > > > > > newer versions since 2.1. Should we care about it?
> > > > > > 
> > > > > > For convenience, we may include both the firmware source and binary in
> > > > > > the CVS repository, so that one can install even without as31.
> > > > > 
> > > > > Yep. I will try to introduce a new configure option like 
> > > > > '--enable-buildfw' for it, or any similar solution.
> > > > 
> > > > That'll be nice.
> > > 
> > > Here it is. The new configure option for alsa-firmware is called 
> > > '--enable-buildfw'. If you want to build it from source you have to 
> > > install one of the latest versions of as31, which you can find at
> > > 
> > > http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> > > 
> > > (e.g. version 2.3.0 is fine)
> > 
> > Thanks, I added it to CVS now.
> > 
> > Could you prepare some document about as31?
> > Just mention the above in README of usx2yloader would suffice.
> 
> Of course, also including a small GPL copyright note.
> 
> martin
> 
> Summary: text added for building usx2y-fw from source file
> Signed-off-by: Martin Langer <martin-langer@gmx.de>

Thanks, applied.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

Re: [RFC] re-queuing usx2y-fw

[Thierry Vignaud]

Martin Langer <martin-langer@gmx.de> writes:

> > > > > The code still depends on as31 (8031/8051 crosss-assembler)
> > > > > which still isn't available as .rpm or .deb, at least newer
> > > > > versions since 2.1. Should we care about it?
> > > > 
> > > > For convenience, we may include both the firmware source and
> > > > binary in the CVS repository, so that one can install even
> > > > without as31.
> > > 
> > > Yep. I will try to introduce a new configure option like
> > > '--enable-buildfw' for it, or any similar solution.
> > 
> > That'll be nice.
> 
> Here it is. The new configure option for alsa-firmware is called
> '--enable-buildfw'. If you want to build it from source you have to
> install one of the latest versions of as31, which you can find at
> 
> http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31

why not auto enabling it if we detect the non free as31 rather than
just providing such flag?



-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

Re: [RFC] re-queuing usx2y-fw

[Martin Langer]

On Thu, Mar 31, 2005 at 06:03:41PM +0200, Thierry Vignaud wrote:
> Martin Langer <martin-langer@gmx.de> writes:
> 
> > > > > > The code still depends on as31 (8031/8051 crosss-assembler)
> > > > > > which still isn't available as .rpm or .deb, at least newer
> > > > > > versions since 2.1. Should we care about it?
> > > > > 
> > > > > For convenience, we may include both the firmware source and
> > > > > binary in the CVS repository, so that one can install even
> > > > > without as31.
> > > > 
> > > > Yep. I will try to introduce a new configure option like
> > > > '--enable-buildfw' for it, or any similar solution.
> > > 
> > > That'll be nice.
> > 
> > Here it is. The new configure option for alsa-firmware is called
> > '--enable-buildfw'. If you want to build it from source you have to
> > install one of the latest versions of as31, which you can find at
> > 
> > http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> 
> why not auto enabling it if we detect the non free as31 rather than
> just providing such flag?
> 

BSD license is non free?

Is it really necessary to build it by default? I see a lot of trouble at 
the horizon due to version mismatches of as31. An as31 version check 
could solve it, though.

martin


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

Re: [RFC] re-queuing usx2y-fw

[Takashi Iwai]

At Fri, 1 Apr 2005 12:33:48 +0200,
Martin Langer wrote:
> 
> On Thu, Mar 31, 2005 at 06:03:41PM +0200, Thierry Vignaud wrote:
> > Martin Langer <martin-langer@gmx.de> writes:
> > 
> > > > > > > The code still depends on as31 (8031/8051 crosss-assembler)
> > > > > > > which still isn't available as .rpm or .deb, at least newer
> > > > > > > versions since 2.1. Should we care about it?
> > > > > > 
> > > > > > For convenience, we may include both the firmware source and
> > > > > > binary in the CVS repository, so that one can install even
> > > > > > without as31.
> > > > > 
> > > > > Yep. I will try to introduce a new configure option like
> > > > > '--enable-buildfw' for it, or any similar solution.
> > > > 
> > > > That'll be nice.
> > > 
> > > Here it is. The new configure option for alsa-firmware is called
> > > '--enable-buildfw'. If you want to build it from source you have to
> > > install one of the latest versions of as31, which you can find at
> > > 
> > > http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> > 
> > why not auto enabling it if we detect the non free as31 rather than
> > just providing such flag?
> > 
> 
> BSD license is non free?
> 
> Is it really necessary to build it by default? I see a lot of trouble at 
> the horizon due to version mismatches of as31. An as31 version check 
> could solve it, though.

Agreed.  The resultant firmware should be 100% identical even if you
build by yourself.  Hence I don't think it's needed so much.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30

Re: [RFC] re-queuing usx2y-fw

[Martin Langer]

On Fri, Apr 01, 2005 at 12:52:56PM +0200, Takashi Iwai wrote:
> At Fri, 1 Apr 2005 12:33:48 +0200,
> Martin Langer wrote:
> > On Thu, Mar 31, 2005 at 06:03:41PM +0200, Thierry Vignaud wrote:
> > > Martin Langer <martin-langer@gmx.de> writes:
> > > 
> > > > http://wiki.erazor-zone.de/doku.php?id=wiki:projects:linux:as31
> > > 
> > > why not auto enabling it if we detect the non free as31 rather than
> > > just providing such flag?
> > 
> > Is it really necessary to build it by default? I see a lot of trouble at 
> > the horizon due to version mismatches of as31. An as31 version check 
> > could solve it, though.
> 
> Agreed.  The resultant firmware should be 100% identical even if you
> build by yourself.  Hence I don't think it's needed so much.

Controlling a checksum could solve that. md5sum? That would result in a 
table of as31 version and their related checksum. If someone wants to 
write it, go ahead :)

martin


-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30