linuxdc-dev Mailing List for LinuxDC: Linux for the Sega Dreamcast (Page 37)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Had to commit this last change to CVS twice after making a silly mistake 
(failing to save edited log file, so it didn't update first time round).

Adrian

--- /home/Adrian/sounddc/purupuru.c	Wed Mar 13 23:39:57 2002
+++ ./purupuru.c	Thu Mar 14 18:25:54 2002
@@ -19,8 +19,11 @@
 /*
  * First posted 18 Feburary 2002
  *
- * Multiple device support fixed 7 March 2003
- */
+ * Multiple device support fixed 7 March 2002
+ *
+ * Hot plugging bug fixed 14 March 2002 
+ *
+*/
 
 #include <linux/kernel.h>
 #include <linux/slab.h>
@@ -36,9 +39,9 @@
 #include <linux/interrupt.h>
 
 #define PURU_MINOR_BASE 64
-#define PPP_VERSION 1
+#define PPP_VERSION 2
 
-/*#define _DEBUG_ */
+/*#define _DEBUG_*/
 
 #ifdef _DEBUG_
 #define DEBGM(fmt, args...)  (printk(KERN_ERR fmt, ##args))
@@ -57,6 +60,7 @@
 /* may be more than one puru puru attached */
 LIST_HEAD(devices_list);
 
+static int use_count = 0;
 
 struct dc_puru_effect {
 	int length_of_time;
@@ -71,6 +75,7 @@
 	int minor;
 	atomic_t active;
 	int timeleft;
+       
 
 };
 
@@ -111,7 +116,8 @@
 	puru->dev.event = NULL;
 	puru->dev.idbus = BUS_MAPLE;
 	input_register_device(&puru->dev);
-	input_register_handler(&purupuru_handler);
+	if (use_count == 0) input_register_handler(&purupuru_handler);
+	use_count++;
 
 	return 0;
 
@@ -121,9 +127,10 @@
 {
 	struct dc_purupuru *puru = d->private_data;
 	input_unregister_device(&puru->dev);
-	/* Remove this device from list */
-	list_del(&puru->list);
-	kfree(puru);
+	DEBGM("In dc_purupuru_disconnect\n");
+	use_count--;
+	if (use_count < 0) use_count = 0;
+	if (use_count == 0) input_unregister_handler(&purupuru_handler);
 
 }
 
@@ -410,13 +417,17 @@
 	/* tasklet_enable(&switchoff_tasklet); */
 
 	/* Is this a Puru Puru device? */
-	if (dev->open != dc_puru_open)
+	if (dev->open != dc_puru_open) {
+		DEBGM("Attempted to connect non-PP device\n");
 		return NULL;
+	}
 	/* Have we already added this device? */
 	list_for_each(lst, &devices_list) {
 		device = list_entry(lst, struct dc_purupuru, list);
 		if (device->minor == (PURU_MINOR_BASE + dev->number)) {
-			return NULL;
+			DEBGM
+			    ("Attempting to connect already connected PP\n");
+			return device->dev.handle;
 		}
 	}
 
@@ -439,6 +450,7 @@
 	struct dc_purupuru *dcp = dev->private;
 	dcp->minor = handler->minor;
 	list_add_tail(&dcp->list, &devices_list);
+
 	return handle;
 
 
@@ -454,13 +466,15 @@
 	list_for_each_safe(ptr, nxt, &devices_list) {
 		device = list_entry(ptr, struct dc_purupuru, list);
 		if (device->minor == handle->handler->minor) {
+			DEBGM("Disconnection: removing from list\n");
 			list_del(&device->list);
-			kfree(device);
 		}
 	}
 
 	input_close_device(handle);
 	kfree(handle);
+	kfree(device);
+
 }
 
 static struct input_handler purupuru_handler = {
@@ -475,9 +489,9 @@
 {
 
 	maple_register_driver(&dc_purupuru_driver);
-	printk("Puru Puru Pack driver for Dreamcast Linux version 0.1\n");
+	printk("Puru Puru Pack driver for Dreamcast Linux version 0.2\n");
 	/* tasklet_disable(&switchoff_tasklet); */
-
+	
 	return 0;
 }
 
@@ -488,7 +502,7 @@
 	struct dc_puru_effect *effect;
 
 	maple_unregister_driver(&dc_purupuru_driver);
-	input_unregister_handler(&purupuru_handler);
+	
 
 	if (!list_empty(&effects_list)) {
 		list_for_each_safe(ptr, nxt, &effects_list) {



On Wednesday 13 Mar 2002 11:43 pm, Adrian McMenamin wrote:
> This should allow true hog plugging of the PPP
>
>

Don't use this patch! While it fixes the crash problem with hot plugging, it 
does so at the price of switching off the rumble functionality :-<

I'm working on a proper fix now.

Adrian



This should allow true hog plugging of the PPP


--- /home/Adrian/sounddc/purupuru.c	Wed Mar 13 23:39:57 2002
+++ ./purupuru.c	Wed Mar 13 23:37:41 2002
@@ -19,8 +19,11 @@
 /*
  * First posted 18 Feburary 2002
  *
- * Multiple device support fixed 7 March 2003
- */
+ * Multiple device support fixed 7 March 2002
+ *
+ * Hot plugging bug fixed 13 March 2002 
+ *
+*/
 
 #include <linux/kernel.h>
 #include <linux/slab.h>
@@ -38,7 +41,7 @@
 #define PURU_MINOR_BASE 64
 #define PPP_VERSION 1
 
-/*#define _DEBUG_ */
+/*#define _DEBUG_*/
 
 #ifdef _DEBUG_
 #define DEBGM(fmt, args...)  (printk(KERN_ERR fmt, ##args))
@@ -111,7 +114,7 @@
 	puru->dev.event = NULL;
 	puru->dev.idbus = BUS_MAPLE;
 	input_register_device(&puru->dev);
-	input_register_handler(&purupuru_handler);
+
 
 	return 0;
 
@@ -121,9 +124,7 @@
 {
 	struct dc_purupuru *puru = d->private_data;
 	input_unregister_device(&puru->dev);
-	/* Remove this device from list */
-	list_del(&puru->list);
-	kfree(puru);
+	DEBGM("In dc_purupuru_disconnect\n");
 
 }
 
@@ -410,13 +411,17 @@
 	/* tasklet_enable(&switchoff_tasklet); */
 
 	/* Is this a Puru Puru device? */
-	if (dev->open != dc_puru_open)
+	if (dev->open != dc_puru_open) {
+		DEBGM("Attempted to connect non-PP device\n");
 		return NULL;
+	}
 	/* Have we already added this device? */
 	list_for_each(lst, &devices_list) {
 		device = list_entry(lst, struct dc_purupuru, list);
 		if (device->minor == (PURU_MINOR_BASE + dev->number)) {
-			return NULL;
+			DEBGM
+			    ("Attempting to connect already connected PP\n");
+			return device->dev.handle;
 		}
 	}
 
@@ -454,13 +459,15 @@
 	list_for_each_safe(ptr, nxt, &devices_list) {
 		device = list_entry(ptr, struct dc_purupuru, list);
 		if (device->minor == handle->handler->minor) {
+			DEBGM("Disconnection: removing from list\n");
 			list_del(&device->list);
-			kfree(device);
 		}
 	}
 
 	input_close_device(handle);
 	kfree(handle);
+	kfree(device);
+
 }
 
 static struct input_handler purupuru_handler = {
@@ -475,9 +482,9 @@
 {
 
 	maple_register_driver(&dc_purupuru_driver);
-	printk("Puru Puru Pack driver for Dreamcast Linux version 0.1\n");
+	printk("Puru Puru Pack driver for Dreamcast Linux version 0.2\n");
 	/* tasklet_disable(&switchoff_tasklet); */
-
+	input_register_handler(&purupuru_handler);
 	return 0;
 }
 



On Wednesday 13 Mar 2002 6:38 am, David Willmore wrote:
> >  I'm trying to create a bootable linux CD and I can't seem to get it to
> > work. Is this a proper forum to ask about creating bootable CD's?
> >
> >  I tried the master.sh and also followed the instructions on the mc.pp.se
> > site. I'm guessing it could be my burner? It's a Microimages backpack CD.
> >
> >  I can boot from a CD my friend made me a few months ago using Nero I
> > think.
>
> I walked through the instructions twice on two seperate occasions and
> have never had any luck.  I think I'm hung up on getting a good IP.BIN
> as I don't have any existing DC software to snag a copy from.  I found
> a tool that claimed to make one, but the resulting disk doesn't read.
>
It can be done, I assure you! What is going wrong? Just coasters? Have you 
looked at http://www.fivemouse.com? It has some instructions too...


> I'd sure love to have a working procedure, too.
>
> Hard to develop code when you can't run it. :(  Not that anyone will
> be interested in the stuff I'd be porting as it's all wierd amateur
> radio digital stuff. :)
>
> Is there any cheap sound input for the DC?  I can get line level
> audio and I just need to sample it at 8KHz/16bit or such.  Is there
> a cheap Maple device that does that?  I bought my DC for software
> development and have never played a game on it. :)  I have no idea
> what kinds of controllers are available for it--except for the
> cool recent puru puru posts, that is.  I'm not sure if I can think
> of a use for vibration in my application. :)
>
There is a microphone which I am trying to write a driver for. But while I 
have made some progress I haven't got anything actually working yet :-<


> Cheers,
> David N0YMV
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev



>  I'm trying to create a bootable linux CD and I can't seem to get it to 
> work. Is this a proper forum to ask about creating bootable CD's?
> 
>  I tried the master.sh and also followed the instructions on the mc.pp.se
> site. I'm guessing it could be my burner? It's a Microimages backpack CD.
>  
>  I can boot from a CD my friend made me a few months ago using Nero I
> think.

I walked through the instructions twice on two seperate occasions and
have never had any luck.  I think I'm hung up on getting a good IP.BIN
as I don't have any existing DC software to snag a copy from.  I found
a tool that claimed to make one, but the resulting disk doesn't read.

I'd sure love to have a working procedure, too.

Hard to develop code when you can't run it. :(  Not that anyone will
be interested in the stuff I'd be porting as it's all wierd amateur
radio digital stuff. :)

Is there any cheap sound input for the DC?  I can get line level
audio and I just need to sample it at 8KHz/16bit or such.  Is there
a cheap Maple device that does that?  I bought my DC for software
development and have never played a game on it. :)  I have no idea
what kinds of controllers are available for it--except for the
cool recent puru puru posts, that is.  I'm not sure if I can think
of a use for vibration in my application. :)

Cheers,
David N0YMV



 I'm trying to create a bootable linux CD and I can't seem to get it to 
work. Is this a proper forum to ask about creating bootable CD's?

 I tried the master.sh and also followed the instructions on the mc.pp.se
site. I'm guessing it could be my burner? It's a Microimages backpack CD.
 
 I can boot from a CD my friend made me a few months ago using Nero I
think.
 




On Saturday 09 Mar 2002 10:53 pm, M. R. Brown wrote:

>
> The 2MB and 4MB doesn't correspond to megabytes, unfortunately, and from my
> understanding those cards are bank-switched, which means you can't access
> the full 256k or 512k range without manually toggling a switch.  Heh, you
> might want to look up and see if anyone's ever done a CF to Maple adapter
>
> :P.

CF == Compact Flash. I see.

>
> M. R.



On Saturday 09 Mar 2002 10:53 pm, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Sat, Mar 09, 2002:
> > I've just bought a 2MB and a 4MB memory card on ebay and was wondering
> > what the state of driver support for these and other devices (ie VMU) was
> > at.
> >
> > I remember a discussion about all this some time back on the list but it
> > didn't seem conclusive.
> >
> > I know one idea that was discussed was booting Linux off an image stored
> > on one of these devices - is that a realistic possibility?
>
> The 2MB and 4MB doesn't correspond to megabytes, unfortunately, and from my
> understanding those cards are bank-switched, which means you can't access
> the full 256k or 512k range without manually toggling a switch.  Heh, you
> might want to look up and see if anyone's ever done a CF to Maple adapter
>
> :P.
>
Sounds like I've been done. Oh well, c'est la vie and all that. CF? Don't 
understand that.


> M. R.



* Adrian McMenamin <ad...@mc...> on Sat, Mar 09, 2002:

> I've just bought a 2MB and a 4MB memory card on ebay and was wondering wh=
at=20
> the state of driver support for these and other devices (ie VMU) was at.
>=20
> I remember a discussion about all this some time back on the list but it=
=20
> didn't seem conclusive.=20
>=20
> I know one idea that was discussed was booting Linux off an image stored =
on=20
> one of these devices - is that a realistic possibility?
>=20

The 2MB and 4MB doesn't correspond to megabytes, unfortunately, and from my
understanding those cards are bank-switched, which means you can't access
the full 256k or 512k range without manually toggling a switch.  Heh, you
might want to look up and see if anyone's ever done a CF to Maple adapter
:P.

M. R.

* Adrian McMenamin <ad...@mc...> on Sat, Mar 09, 2002:

> I know that it is on the "to do" list, but I'm pretty certain nothing has=
=20
> happened in any practical sense. I'm afarid a net driver is somewhat beyo=
nd=20
> my abilities at present - so it wouldn't be me doing it.
>=20

I'm still waiting on my Lan Adapter to arrive - I plan on writing a net
driver for it as soon as I get it, but no idea on how long that would take.

M. R.

I've just bought a 2MB and a 4MB memory card on ebay and was wondering what 
the state of driver support for these and other devices (ie VMU) was at.

I remember a discussion about all this some time back on the list but it 
didn't seem conclusive. 

I know one idea that was discussed was booting Linux off an image stored on 
one of these devices - is that a realistic possibility?

Adrian



On Saturday 09 Mar 2002 12:55 pm, andrea wrote:
> Hi,
> do you know if the LAN adapter (the HIT-300 japanese
> model) is also supported in LinuxDC? I know the
> Broadband Adapter (HIT-4X00) is supported.
>
> thanks
>
> -A
>
>
I know that it is on the "to do" list, but I'm pretty certain nothing has 
happened in any practical sense. I'm afarid a net driver is somewhat beyond 
my abilities at present - so it wouldn't be me doing it.

I've copied this to the list to see if anyone else would like to comment.

Adrian



On Saturday 02 Mar 2002 2:04 am, RC5Stint wrote:
> > Adrian McMenamin on Sat, Mar 02, 2002:
> > > I am not sure what the winder is - a new function or just
> > > something that already exists repackaged?
>
> As you probably know, the Dreamcast controller driver supports
> controllers with a "second joystick".  Perhaps the fishing rod is
> just a standard controller and Puru Puru encased together into this
> rod-like thing, and the winder reports its "value" as a second
> joystick?

Just to answer this. The Naki fishing rod registers both as a DC controller 
and a Puru Puru Pack (ie Maple sees it as two devices even though we see it 
only as one).



To properly support multiple devices (including fishing rods :-> ):

--- /home/Adrian/sounddc/purupuru.c	Thu Mar  7 00:31:51 2002
+++ ./purupuru.c	Thu Mar  7 00:24:13 2002
@@ -19,6 +19,7 @@
 /*
  * First posted 18 Feburary 2002
  *
+ * Multiple device support fixed 7 March 2003
  */
 
 #include <linux/kernel.h>
@@ -37,7 +38,7 @@
 #define PURU_MINOR_BASE 64
 #define PPP_VERSION 1
 
-#define _DEBUG_
+/*#define _DEBUG_ */
 
 #ifdef _DEBUG_
 #define DEBGM(fmt, args...)  (printk(KERN_ERR fmt, ##args))
@@ -111,9 +112,7 @@
 	puru->dev.idbus = BUS_MAPLE;
 	input_register_device(&puru->dev);
 	input_register_handler(&purupuru_handler);
-	puru->minor = ((puru->dev.handle)->handler)->minor;
-	/* Add this device to the list */
-	list_add_tail(&puru->list, &devices_list);
+
 	return 0;
 
 }
@@ -368,6 +367,7 @@
 
 void dc_purupuru_wake(struct maple_driver_data *data)
 {
+
 	if (last_jiffies == -1) {
 		last_jiffies = jiffies;
 		return;
@@ -405,10 +405,21 @@
 					     struct input_dev *dev)
 {
 	struct input_handle *handle;
+	struct list_head *lst;
+	struct dc_purupuru *device;
+	/* tasklet_enable(&switchoff_tasklet); */
 
 	/* Is this a Puru Puru device? */
 	if (dev->open != dc_puru_open)
 		return NULL;
+	/* Have we already added this device? */
+	list_for_each(lst, &devices_list) {
+		device = list_entry(lst, struct dc_purupuru, list);
+		if (device->minor == (PURU_MINOR_BASE + dev->number)) {
+			return NULL;
+		}
+	}
+
 	if (!(handle = kmalloc(sizeof(struct input_handle), GFP_KERNEL)))
 		return NULL;
 	memset(handle, 0, sizeof(struct input_handle));
@@ -420,9 +431,14 @@
 
 	printk(KERN_INFO "purupuru.c: adding Puru Puru Pack  input%d\n",
 	       dev->number);
-	tasklet_enable(&switchoff_tasklet);
+
 
 	handler->minor = PURU_MINOR_BASE + dev->number;
+
+	/* Add to list */
+	struct dc_purupuru *dcp = dev->private;
+	dcp->minor = handler->minor;
+	list_add_tail(&dcp->list, &devices_list);
 	return handle;
 
 
@@ -430,6 +446,19 @@
 
 static void purupuru_disconnect(struct input_handle *handle)
 {
+	/* Remove from list of devices */
+	struct list_head *ptr = NULL;
+	struct list_head *nxt = NULL;
+	struct dc_purupuru *device;
+
+	list_for_each_safe(ptr, nxt, &devices_list) {
+		device = list_entry(ptr, struct dc_purupuru, list);
+		if (device->minor == handle->handler->minor) {
+			list_del(&device->list);
+			kfree(device);
+		}
+	}
+
 	input_close_device(handle);
 	kfree(handle);
 }
@@ -447,7 +476,7 @@
 
 	maple_register_driver(&dc_purupuru_driver);
 	printk("Puru Puru Pack driver for Dreamcast Linux version 0.1\n");
-	tasklet_disable(&switchoff_tasklet);
+	/* tasklet_disable(&switchoff_tasklet); */
 
 	return 0;
 }



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Adrian McMenamin on Sat, Mar 02, 2002:
> 
> > I am not sure what the winder is - a new function or just 
> > something that already exists repackaged?

As you probably know, the Dreamcast controller driver supports
controllers with a "second joystick".  Perhaps the fishing rod is
just a standard controller and Puru Puru encased together into this
rod-like thing, and the winder reports its "value" as a second
joystick?

- --
RC5Stint <rc5...@ya...>
PGP Key ID: 0x3B4BEC6F

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32) - WinPT 0.5.1
Comment: For info see http://www.gnupg.org

iD8DBQE8gDL3ifMcQztL7G8RAjKTAJ4kokQc96upElgMsXivGzsQkS1EUQCdFeGY
mMljJu4oEzarQtT0dC0MlGc=
=RHqp
-----END PGP SIGNATURE-----

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com




* Adrian McMenamin <ad...@mc...> on Sat, Mar 02, 2002:

>=20
> Possibly, though I am not sure what the winder is - a new function or jus=
t=20
> something that already exists repackaged?
>=20

Do you have a dump of the functions reported from device info?

M. R.

On Friday 01 Mar 2002 10:33 pm, M. R. Brown wrote:

> Anything relevant is already handled by Maple in the kernel.
>
> M. R.

Possibly, though I am not sure what the winder is - a new function or just 
something that already exists repackaged?



* M. R. Brown <mr...@0x...> on Fri, Mar 01, 2002:

>=20
> > Any thoughts?
>=20
> Remember that Maple devices export "functions" of what they can do, so the
> vibration function of the fishing rod could be handled by the puru-puru
> driver while the controller portion (or whatever) could be handled by the
> Maple controller code (if it is indeed a controller) or by the general
> purpose Maple layer.
>=20

Hmm, given the list of usable/existing Maple functions, wouldn't the
fishing rod have to fall into one of the following categories?

#define MAPLE_FUNC_CONTROLLER 0x001
#define MAPLE_FUNC_MEMCARD    0x002
#define MAPLE_FUNC_LCD        0x004
#define MAPLE_FUNC_CLOCK      0x008
#define MAPLE_FUNC_MICROPHONE 0x010
#define MAPLE_FUNC_ARGUN      0x020
#define MAPLE_FUNC_KEYBOARD   0x040
#define MAPLE_FUNC_LIGHTGUN   0x080
#define MAPLE_FUNC_PURUPURU   0x100
#define MAPLE_FUNC_MOUSE      0x200

Anything relevant is already handled by Maple in the kernel.

M. R.



* Adrian McMenamin <ad...@mc...> on Fri, Mar 01, 2002:

> I know the (previous) general view about devices such as the fishing rod =
is=20
> that there should be no kernel space driver for them.
>=20
> But I've just had one delivered and it appears to respond to existing dri=
vers=20
> anyway (at least puru puru drives rumbling).
>=20
> What is the consequence for previous plans for this?
>=20

Like I said before, if such a "bastard" device is supported by an already
existing kernel Maple interface, then your work is already done.  Otherwise,
your interests are best served with a general purpose Maple driver that
can directly interface userapps with peculiar Maple devices.

> Any thoughts?

Remember that Maple devices export "functions" of what they can do, so the
vibration function of the fishing rod could be handled by the puru-puru
driver while the controller portion (or whatever) could be handled by the
Maple controller code (if it is indeed a controller) or by the general
purpose Maple layer.

M. R.

Now I have a fishing rod I have discovered another bug in the puru puru 
driver - it doesn't work properly in environments where there is more than 
one PP device installed - won't stop rumbling once started.

I'll endeavour to fix.

Adrian



I know the (previous) general view about devices such as the fishing rod is 
that there should be no kernel space driver for them.

But I've just had one delivered and it appears to respond to existing drivers 
anyway (at least puru puru drives rumbling).

What is the consequence for previous plans for this?

Any thoughts?

Adrian



On Tuesday 26 Feb 2002 11:55 pm, Adrian McMenamin wrote:

>
> 0x0f followed by....	0x00 generates a -3 response
> 		   0x01 generates an 0x08 response
>
> 		   0x02 generates an 0x07 response
> 		      0x0002 returns 0x00 0x00 0x00 0x10 0x00 0x00 0x00 0x00 from (a
>                                                             subsequent)
> 0x01 0x0102 returns 0x00 0x00 0x00 0x10 0x02 0x00 0x00 0x00 from 0x01
> 0x0202 returns -3
>


As an additional point

0x@@01 (where 0x20 < 0x@@ > 0x01) returns 0x00 0x00 0x00 0x10 0x00 0x@@ 0x00 
0x00



I was writing a microphone driver for Linux - couldn't get very far, so wrote 
a Puru Puru driver instead - but now that's done I'm back to the 
microphone....

The microphone responds to Maple command 15 (0x0f) - (read 
http://mc.pp.se/dc/maplebus.html to understand what this means).

A command of 0x0e, 0x01 generates an 0x08 response (ie a data transfer) - 
with 8 bytes transfered (other than the standard 32 bit command 
acknowledgement) - and the 'default' appears to be 0x00, 0x00, 0x00, 0x10, 
0x00, 0x00, 0x00, 0x00 - but other commands appear to generate slighly 
different responses...

 
0x0f followed by....	0x00 generates a -3 response
		   0x01 generates an 0x08 response

		   0x02 generates an 0x07 response
		      0x0002 returns 0x00 0x00 0x00 0x10 0x00 0x00 0x00 0x00 from (a 	      
                                                            subsequent) 0x01
		      0x0102 returns 0x00 0x00 0x00 0x10 0x02 0x00 0x00 0x00 from 0x01
		      0x0202 returns -3

		   0x03 generates an 0x07 response
		      0x0103 generates an 0x07 response and default from 0x01
		      0x0203 generates an 0x07 response and default from 0x01
		      0x0303 as above
		      0x0403 as above
		      0x0503 as above
		     0xff03 generates a -3

		   0x04 generates an 0x07 repsonse
		      0x0104 generates default response from 0x01
		      0x0204 generates 0x00 0x00 0x00 0x10 0x10 0x00 0x00 0x00 from 0x01
		      0x0304 generates -3

		   0x05 generates a -3 response

		   0x08 generates a -3 response

		   0x09 generates a -3 response

(sorry this is written shorthand - but I hope you understand)

Anyway, point is, can anyone suggest what any of this might mean... any 
guesses welcome.

0x10 == 16 bit sampling, seems one obvious conclusion, sort of...

Before anyone asks the block read and get condition commands appear to 
generate a -3 response in all conditions I've tested for, so they (seem) 
useless as a means of transferring data from the microphone.

0x10, 0x11 and 0x12 as basic commands also appear to generate -3 responses.

Anyway, any thoughts?

Adrian



Sorry for the cold email but I appreciate you may normally be bombarded by=
 telephone calls throughout the day=2E

JPL Group specialise in the placement of SOFTWARE/HARDWARE DSP, EMBEDDED E=
NGINEERS suitable for
Software/Hardware Houses and Major Electronic Manufacturers=2E

Innovations in Digital Signal Processing (DSP) have sparked a digital revo=
lution=2EDSP's are at the centre of modern communications, whilst applicat=
ions such as internet audio, digital still cameras and digital radio are i=
ncreasing the appetite for DSP's=2E With the shift to digital embedded sys=
tems design, now in software rather than hardware, demand for skilled Deve=
lopers is high=2E

JPL Group can provide high calibre candidates who are experts in their fie=
ld from our continually updated network of actively looking DSP profession=
als=2E

As you can see from our website at www=2Ejplg=2Ecom we are specialists in =
our field and therefore understand your industry and your particular secto=
r, therefore we are able to provide staff which best suit your requirement=
s=2E

We would be pleased to assist you with any current requirements for staff =
that you may have and should this be the case then please do not hesitate =
to contact us or forward your vacancy requirements to us via email=2E

If you are not currently looking to employ any new staff then please keep =
our details for future reference=2E

Regards

Paul Szczepanski
JPL Group
Telephone: 0870 800 9493
Fax: 0870 800 9495
Take a look at our interactive website at www=2Ejplg=2Ecom






2000	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (19)
2001	Jan (13)	Feb (12)	Mar (14)	Apr (3)	May (25)	Jun	Jul (9)	Aug	Sep (47)	Oct (24)	Nov (23)	Dec (58)
2002	Jan (87)	Feb (54)	Mar (38)	Apr (6)	May (11)	Jun (7)	Jul (13)	Aug (39)	Sep (58)	Oct (20)	Nov (63)	Dec (46)
2003	Jan	Feb	Mar (8)	Apr (52)	May (21)	Jun (2)	Jul (10)	Aug	Sep (6)	Oct (1)	Nov (1)	Dec (1)
2004	Jan	Feb (2)	Mar	Apr (1)	May (5)	Jun (46)	Jul (15)	Aug (1)	Sep (12)	Oct (3)	Nov (4)	Dec
2005	Jan	Feb (2)	Mar (1)	Apr	May	Jun	Jul (2)	Aug (6)	Sep	Oct	Nov	Dec (2)
2006	Jan	Feb	Mar	Apr	May	Jun (1)	Jul (5)	Aug (2)	Sep (2)	Oct (3)	Nov (7)	Dec (2)
2007	Jan (8)	Feb (16)	Mar (17)	Apr (16)	May (21)	Jun (17)	Jul (40)	Aug (62)	Sep (30)	Oct (14)	Nov (7)	Dec (9)
2008	Jan (4)	Feb (7)	Mar (36)	Apr (22)	May (21)	Jun (9)	Jul (35)	Aug (17)	Sep (21)	Oct (24)	Nov (61)	Dec (85)
2009	Jan (51)	Feb (36)	Mar (60)	Apr (77)	May (154)	Jun (118)	Jul (86)	Aug (30)	Sep (20)	Oct (31)	Nov (10)	Dec (25)
2010	Jan (15)	Feb (17)	Mar (38)	Apr (59)	May (84)	Jun (63)	Jul (39)	Aug (43)	Sep (12)	Oct (6)	Nov (2)	Dec (2)
2011	Jan (2)	Feb	Mar (3)	Apr (1)	May	Jun (3)	Jul (2)	Aug (1)	Sep (3)	Oct (1)	Nov (4)	Dec (1)
2012	Jan (3)	Feb (1)	Mar (4)	Apr	May (1)	Jun (3)	Jul (1)	Aug (2)	Sep (3)	Oct (1)	Nov (1)	Dec (3)
2013	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (4)	Sep (7)	Oct (8)	Nov (1)	Dec (9)
2014	Jan (8)	Feb (4)	Mar (3)	Apr (3)	May (7)	Jun (2)	Jul (5)	Aug (5)	Sep (3)	Oct (11)	Nov (5)	Dec (6)
2015	Jan (2)	Feb (2)	Mar (2)	Apr (5)	May (3)	Jun	Jul (4)	Aug	Sep	Oct (1)	Nov (1)	Dec (1)
2016	Jan (1)	Feb	Mar (4)	Apr (3)	May (7)	Jun (2)	Jul (1)	Aug (3)	Sep (1)	Oct (1)	Nov (1)	Dec (3)
2017	Jan	Feb (1)	Mar (2)	Apr (3)	May (2)	Jun	Jul	Aug	Sep	Oct	Nov	Dec

linuxdc-dev Mailing List for LinuxDC: Linux for the Sega Dreamcast (Page 37)

linuxdc-dev — Developer discussion list