linuxdc-dev — Developer discussion list

Re: [linuxdc-dev] Linux Programming

[<ps...@wi...>]

What do you intend to do with the katana dev machine? Or, that is to say, what does it offer that a standard dreamcast does not? Hard-drive space and easier booting?

Re: [linuxdc-dev] Linux Programming

[Ben S. <sr...@cs...>]

I'm basically also just getting started with doing LinuxDC development.
I've spent more of my time doing KOS programming.

How much do you really need a keyboard and if so where do you suggest
getting one? (cheap)

Ben

-- 
Ben Srour
sr...@cs...

On Fri, 1 Nov 2002, Jason Dodson wrote:

> Thanks... youre my hero.
>
>
> ----- Original Message -----
> From: "M. R. Brown" <mr...@0x...>
> To: "Jason Dodson" <min...@ya...>
> Cc: <lin...@li...>
> Sent: Friday, November 01, 2002 2:58 PM
> Subject: Re: [linuxdc-dev] Linux Programming
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

Re: [linuxdc-dev] Linux Programming

[Jason D. <min...@ya...>]

Thanks... youre my hero.


----- Original Message ----- 
From: "M. R. Brown" <mr...@0x...>
To: "Jason Dodson" <min...@ya...>
Cc: <lin...@li...>
Sent: Friday, November 01, 2002 2:58 PM
Subject: Re: [linuxdc-dev] Linux Programming

Re: [linuxdc-dev] Linux Programming

[M. R. B. <mr...@0x...>]

* Jason Dodson <min...@ya...> on Fri, Nov 01, 2002:

> Ok, Ive been lingering on this list for quite some time, not doing anythi=
ng
> openly... mainly because the development I was doing thus far was a bit o=
dd,
> and not really directly in relation to the kernel. Anyway, I just recently
> obtained a Dreamcast Katana Dev machine, and I want to start actually
> contributing to this. What I NEED though is someplace that can explain HOW
> to write kernel code... drivers of course more specifically. Can someone
> offer a page or even a not-so-expensive-book?
>=20

www.kernelnewbies.org.

Look for the _Linux_Device_Drivers_ book, it should be linked to from
kernelnewbies, it's free online.

M. R.

[linuxdc-dev] Linux Programming

[Jason D. <min...@ya...>]

Ok, Ive been lingering on this list for quite some time, not doing anything
openly... mainly because the development I was doing thus far was a bit odd,
and not really directly in relation to the kernel. Anyway, I just recently
obtained a Dreamcast Katana Dev machine, and I want to start actually
contributing to this. What I NEED though is someplace that can explain HOW
to write kernel code... drivers of course more specifically. Can someone
offer a page or even a not-so-expensive-book?

Thanks

Re: [linuxdc-dev] patch for non-sega keyboards

[M. R. B. <mr...@0x...>]

* Mike Barnett <mik...@ho...> on Fri, Nov 01, 2002:

>     This is my first attempt at a kernel patch, so my apologies if it doe=
sn't work or screws up your kernel sources.  It shouldn't but you never kno=
w.
>=20
>     The bug in the maple.c driver caused non-sega keyboards to continuous=
ly "connect" and "disconnect".  I've tested the patch with a non-sega keybo=
ard and a sega controller.  Both seem to work fine and I would expect other=
 devices to work as well.
>=20
>     Not sure what the process is to get this into the source tree.
>=20

Thanks for the patch.  Applied.

M. R.


2002-11-01  M. R. Brown  <mr...@li...>

	From Mike Barnett:
	* drivers/maple/maple.c (maple_dma_irq): Make sure
	maple_detect_callback() is called if the previous command was
	MAPLE_COMMAND_DEVINFO.

[linuxdc-dev] LinuxDC 2.4.19 / Linux-SH 2.4.20-pre11

[M. R. B. <mr...@0x...>]

LinuxDC 2.4.19 has been released.  Linux-SH 2.4.20-pre11 has been merged
into CVS.

Ok, I've figured out how I want to do this.  Because the kernel that sits
in CVS is always "current", it isn't released until the next version is
merged from upstream.  The "LinuxDC 2.4.19" portion refers to the new
kernel release, the "Linux-SH 2.4.20-pre11" portion refers to what's
"current" in CVS.  Linux-SH of course refers to our parent project at
http://linux-sh.org/.

What does a release mean?  Well, I haven't finished the
auto{build,packaging} scripts, so no, there aren't any files to downlowd
yet.  But it does mean that the released kernel version has been at least
tested that it boots and doesn't oops on LinuxDC drivers.

ChangeLog is everything that changed since the last merge -> release.

M. R.


2002-10-26  M. R. Brown  <mr...@li...>

	Linux-SH 2.4.19

	* AGAINST-2.4.19: New file.
	* AGAINST-2.4.18: Removed.

	* Makefile, drivers/mtd/maps/Makefile, drivers/sound/Config.in,
	drivers/sound/Makefile: Merge changes from Linux-SH 2.4.19.

[linuxdc-dev] Linux-SH 2.4.19

[M. R. B. <mr...@0x...>]

Tested and boots fine on DC with all linuxdc drivers enabled.

Also, I've split CVS into two branches.  HEAD will diverge towards the
Linux 2.5 series -- do NOT checkout HEAD (unstable) unless you're planning
on doing 2.5 development.  If you want the 2.4 (stable) branch, you need to
check out the linux-sh-dc-2_4-branch from CVS:

$ cvs -d... co -r linux-sh-dc-2_4-branch -d linux-sh-dc-2.4-branch \
    linux-sh-dc

Consult your local CVS manual pages if you have any questions.

M. R.


2002-10-26  M. R. Brown  <mr...@li...>

	Linux-SH 2.4.19

	* AGAINST-2.4.19: New file.
	* AGAINST-2.4.18: Removed.

	* Makefile, drivers/mtd/maps/Makefile, drivers/sound/Config.in,
	drivers/sound/Makefile: Merge changes from Linux-SH 2.4.19.

[linuxdc-dev] More Powerful SEX available!! Stronger and long-lasting. Make your partner happ

[<mwo...@ya...>]

Are you enbarrased about short life?  Do you wanna have more vitality?  Do you wanna make your partner happy?

Mazimize your life today with this best-selling Doctor-approved pill.

100% MONEY BACK GUARANTEED.  Why wait?  Click the link below

http://www.ccipowergriphosting.com/business/vitality/



Click on the link below to remove yourself
http://www.ccipowergripresponder.com/cgi-bin/varpro/29.cgi?id=vitality&a=lin...@li...

AOL Users
<a href="http://www.ccipowergripresponder.com/cgi-bin/varpro/29.cgi?id=vitality&a=lin...@li..."> Remove Me</a>

[linuxdc-dev] LinuxDC website...

[M. R. B. <mr...@0x...>]

...has been updated with current information.  Yes, I plan to have a
working website out by November 7th.  This will happen after I finish up
some much needed kernel work and write some much needed LinuxDC
documentation.  I'll defer the generation of operating system packages to
another maintainer, but I'll claim responsibility for generating
busybox+uClibc images.  This will happen after I figure out how to
autogenerate kernel images, and will probably happen before the website is
out.

We are also planning to move kernel development into the 2.5 series fairly
quickly.  What will end up happening is that the 2.4 series kernels will
only be touched (by me) for bugfixes and 2.5 backports, and development
will concentrate on the 2.5 tree.  More on that later.

M. R.

Re: [linuxdc-dev] hello

[Erik A. <and...@co...>]

On Sat Oct 19, 2002 at 09:32:07AM -0600, Erik wrote:
> Looks like I forgot a small piece...  001-linux-sh_2.4.20-pre10=20
> also needs the following, which I forgot to include in my patch
> (I have now updated the patch on my webpage).

And yet another missing piece...  Turns out the BBA is connected
via PCI, but I'd failed to adapt that part for the new kernel.
Here is yet another fix.

--- arch/sh/kernel/pcibios.c.orig	2002-10-19 03:37:25.000000000 -0600
+++ arch/sh/kernel/pcibios.c	2002-10-21 19:11:13.000000000 -0600
@@ -73,7 +73,7 @@
 	}
 }
=20
-int pcibios_enable_device(struct pci_dev *dev)
+int pcibios_enable_device(struct pci_dev *dev, int mask)
 {
 	u16 cmd, old_cmd;
 	int idx;
@@ -82,6 +82,9 @@
 	pci_read_config_word(dev, PCI_COMMAND, &cmd);
 	old_cmd =3D cmd;
 	for(idx=3D0; idx<6; idx++) {
+		/* Only set up the requested stuff */
+		if (!(mask & (1<<idx)))
+			continue;
 		r =3D &dev->resource[idx];
 		if (!r->start && r->end) {
 			printk(KERN_ERR "PCI: Device %s not available because of resource colli=
sions\n", dev->slot_name);

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

[linuxdc-dev] Still no kernel

[Mike B. <mik...@ho...>]

I'm now on my 3rd week of trying to get the current kernel to build and
boot.

A recap...

I can build & boot Bill Gatliff's distribution
I built a new toolchain - binutils 2.11.2, gcc 3.0.4
Pulled and treelinked the SH & DC sources
Linked in the kernel tree into Bill's tree
Built latest kernel using old & new tools both (didn't seem to affect the
outcome)
Burned the CD
Boots result in constant reboots on the DC

I'm beginning to think that the boot environment that Bill's distribution
uses isn't compatible with the current CVS tree.  I would like to get a
complete setup that mirrors exactly another developers environment.

I spent the entire weekend doing builds and boots.  Something's just not
right about what I'm doing.   Another week of this and I'll go nuts.  I've
invested in all the equipment needed including keyboard, mouse, microphone,
bba, etc and don't want to have to ditch it all just because I can't do a
build of the latest sources.

-mike

Re: [linuxdc-dev] Fwd: Kernel building

[Mike B. <mik...@ho...>]

  I am trying to build off of the setup that Bill G made.  Since I was
able to build and boot Gatliff's setup, I figured it was a great place to
start.  As I think I mentioned before, I'm taking the kernel tree that I
downloaded and treelinked, and linking it into Bill's tree where he had a
"kernel" directory.    That should work, in theory.
    I didn't want to change too many variables at one time.  If I can get it
to boot under that setup, then I can move onto something a little more
fancy.
    I'm working my way through another document on how to build the SH
toolchain.  It's somewhat down-rev, but it a good cross-reference to the
instructions you've given .  Basically the same, but he's got some verbiage
about each step.
    As I think I mentioned, I'm having trouble getting all the files you
suggested.  The version numbers don't seem to match up on the FTP site
(binutils 2.13 doesn't exist)

Thanks for all the help.  Hoping to be a productive contributor soon.

mike


----- Original Message -----
From: "M. R. Brown" <mr...@0x...>
To: "Mike Barnett" <mik...@ho...>
Cc: <lin...@li...>
Sent: Sunday, October 20, 2002 8:08 AM
Subject: Re: [linuxdc-dev] Fwd: Kernel building


* Mike Barnett <mik...@ho...> on Sat, Oct 19, 2002:

>
> Could someone email out a simple .config fiile so Matt and I can
> troubleshoot
> this problem?
>

Attached.  How are you booting these kernels?

M. R.

Re: [linuxdc-dev] Fwd: Kernel building

[M. R. B. <mr...@0x...>]

* Mike Barnett <mik...@ho...> on Sat, Oct 19, 2002:

> 
> Could someone email out a simple .config fiile so Matt and I can
> troubleshoot
> this problem?
> 

Attached.  How are you booting these kernels?

M. R.

Re: [linuxdc-dev] Fwd: Kernel building

[Mike B. <mik...@ho...>]

M R Brown pointed out to me recently that having a good config file
is key to getting the kernel build for the DC correct.  I tried building
with
just the linuxSH tree with the branch linux-2_4-branch last night and
without
the linux-dc patches. It had the same reboot problem as before.

Could someone email out a simple .config fiile so Matt and I can
troubleshoot
this problem?

-mike

----- Original Message -----
From: "Matt Gumbel" <mg...@cm...>
To: <lin...@li...>
Sent: Friday, October 18, 2002 6:48 PM
Subject: Re: [linuxdc-dev] Fwd: Kernel building


> On Fri, Oct 18, 2002 at 07:06:10PM +0100, Adrian McMenamin wrote:
> >   13.. Boot in DC.  I get the initial Logo, SEGA splash screen.  And
then the
> >  system resets itself.
> >
> > So what could I be doing wrong?  Do you have a similar set up?
> > Perhaps my down-rev toolchain is causing some problems?
>
> I've mentioned it on this list before, but I'm having this exact
> same problem.  The only difference is that I'm not using
> Gatliff's toolchain, I'm using one I built myself with up to date
> packages.  I can compile and boot older kernels (i.e. the one
> from Gatliff's article) with this toolchain, just not the latest.
>
> My question for you seasoned dc hackers is: What is the best
> known method for debugging issues such as these?  I have the BBA,
> keyboard and mouse at my disposal.
>
> thanks,
> Matt
>
> --
> Matt Gumbel <mg...@cm...>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> Access Your PC Securely with GoToMyPC. Try Free Now
> https://www.gotomypc.com/s/OSND/DD
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

Re: [linuxdc-dev] hello

[Erik A. <and...@co...>]

On Sat Oct 19, 2002 at 07:15:54AM -0500, M. R. Brown wrote:
> > For the curious (or the helpful), my patches for 2.4.20-pre10
> > can be found here:
> >     http://codepoet.org/dreamcast/
> >=20
>=20
> Thanks!  I'll grab your patches and integrate them into both the linuxsh
> and linuxdc trees.  I've been busy scrambling to get the bitrotten linuxsh
> tree up to snuff for 2.5 before the freeze, so I'll probably switch our
> experimental linux-sh-dc tree over to 2.5 RSN.

Looks like I forgot a small piece...  001-linux-sh_2.4.20-pre10=20
also needs the following, which I forgot to include in my patch
(I have now updated the patch on my webpage).

--- linux-2.4.19.orig/include/asm-sh/page.h	2001-09-08 13:29:09.000000000 -=
0600
+++ linux/include/asm-sh/page.h	2002-10-19 04:19:45.000000000 -0600
@@ -118,6 +118,9 @@
=20
 #endif
=20
-#endif /* __KERNEL__ */
+#define VM_DATA_DEFAULT_FLAGS	(VM_READ | VM_WRITE | VM_EXEC | \
+				 VM_MAYREAD | VM_MAYWRITE | VM_MAYEXEC)
+
=20
+#endif /* __KERNEL__ */
 #endif /* __ASM_SH_PAGE_H */

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

Re: [linuxdc-dev] hello

[Karl T. K. <ka...@pr...>]

On Sat, 19 Oct 2002 07:15:54 -0500
"M. R. Brown" <mr...@0x...> wrote:

> * Erik Andersen <and...@co...> on Sat, Oct 19, 2002:
> 
> I have built a GCC 3.2 toolchain (based on uClibc even :P) but I haven't
> had a chance to test it yet.  I've attached the patch for 3.2 (Karl, do
> you remember the original location of Kaz' 3.1/3.2 patch?).  It should
> also apply cleanly to stock 3.2.

I mirrored it at least:
http://www.boblycat.org/~karltk/gcc-3.1-branch-tmp.diff.gz

It does apply cleanly to 3.2 as well. However, I ran into the problem of
missing the symbol __fpscr_values, which I believe is supposed to go into
libgcc(_s).a

If memory serves, Kaz mentioned somewhere that the above patch still has
some issues, but whether it was with FPU mode switching or with
multithreaded apps, I cannot recall.

(I think it would be the latter, as even if we put the __fpscr_values into
libgcc.a/libgcc_s.a, we need to take care of each thread having its own
storage area for 

This was with uClibc-0.9.14, gcc-3.2, binutils-2.13 and the above patch.

AFAICT, it only affects programs for which the compiler actually emits FPU
code. 


Kind regards,

Karl T

Re: [linuxdc-dev] hello

[M. R. B. <mr...@0x...>]

* Erik Andersen <and...@co...> on Sat, Oct 19, 2002:

> Hi, I'm new to the list.  I spent some time this morning porting
> the linux-sh and linux-sh-dc kernel trees up to
> linux-2.4.20-pre10.  The ports were not especially difficult and
> the only place that required any violence was the sh watchdog
> driver, which had some conflicts vs the kernel version.

Note the mainline version of the watchdog is more up-to-date than the
linuxsh one, iirc.

> 
> I used the sh toolchain from 
>     ftp://ftp.m17n.org/pub/dodes/debian/
> but I don't have a lot of confidence in gcc 3.0.3 -- I've had
> some bad luck with gcc 3.0 in general, so it may very well be the
> toolchain.  dunno.  What is the recommended toolchain for
> Dreamcast/SH4 kernel hacking?  gcc 3.2 / binutils 2.12.1? 
> 

I recommend stable as being GCC 3.0.4 and binutils 2.13 w/ patches.  The
patches can be found at ftp://ftp.m17n.org/pub/linux-sh/testing/.  Look for
the highest patch revision (0 for GCC 3.0.4 and 6 for binutils 2.11.2).
The binutils 2.11.2 patch should apply cleanly to 2.13.

I have built a GCC 3.2 toolchain (based on uClibc even :P) but I haven't
had a chance to test it yet.  I've attached the patch for 3.2 (Karl, do you
remember the original location of Kaz' 3.1/3.2 patch?).  It should also
apply cleanly to stock 3.2.

> For the curious (or the helpful), my patches for 2.4.20-pre10
> can be found here:
>     http://codepoet.org/dreamcast/
> 

Thanks!  I'll grab your patches and integrate them into both the linuxsh
and linuxdc trees.  I've been busy scrambling to get the bitrotten linuxsh
tree up to snuff for 2.5 before the freeze, so I'll probably switch our
experimental linux-sh-dc tree over to 2.5 RSN.

M. R.

[linuxdc-dev] hello

[Erik A. <and...@co...>]

Hi, I'm new to the list.  I spent some time this morning porting
the linux-sh and linux-sh-dc kernel trees up to
linux-2.4.20-pre10.  The ports were not especially difficult and
the only place that required any violence was the sh watchdog
driver, which had some conflicts vs the kernel version.  I've
given it a quick try (replacing boot/vmlinux in
dreamcast-linux-010605 and burning a CD), but when ecos tries to
load it, it gives me: 
    RedBoot> load -v /boot/vmlinux
    load_elf_image_aborted: seek: attempt to seek backwards" 
Suggestions on how to track down why ecos refuses to load the
kernel image?

I used the sh toolchain from 
    ftp://ftp.m17n.org/pub/dodes/debian/
but I don't have a lot of confidence in gcc 3.0.3 -- I've had
some bad luck with gcc 3.0 in general, so it may very well be the
toolchain.  dunno.  What is the recommended toolchain for
Dreamcast/SH4 kernel hacking?  gcc 3.2 / binutils 2.12.1? 

For the curious (or the helpful), my patches for 2.4.20-pre10
can be found here:
    http://codepoet.org/dreamcast/

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

Re: [linuxdc-dev] Fwd: Kernel building

[Matt G. <mg...@cm...>]

On Fri, Oct 18, 2002 at 07:06:10PM +0100, Adrian McMenamin wrote:
>   13.. Boot in DC.  I get the initial Logo, SEGA splash screen.  And then the
>  system resets itself.
> 
> So what could I be doing wrong?  Do you have a similar set up?
> Perhaps my down-rev toolchain is causing some problems?

I've mentioned it on this list before, but I'm having this exact
same problem.  The only difference is that I'm not using
Gatliff's toolchain, I'm using one I built myself with up to date
packages.  I can compile and boot older kernels (i.e. the one
from Gatliff's article) with this toolchain, just not the latest. 

My question for you seasoned dc hackers is: What is the best
known method for debugging issues such as these?  I have the BBA,
keyboard and mouse at my disposal.

thanks,
Matt

-- 
Matt Gumbel <mg...@cm...>

[linuxdc-dev] Errr.... corrected patch

[Adrian M. <ad...@mc...>]

Typo in the last one!

--- main.c	Fri Oct 18 21:05:18 2002
+++ linux-sh-dc/drivers/sound/aica/main.c	Fri Oct 18 22:35:34 2002
@@ -68,6 +68,10 @@
 static int currentpoint;
 static struct semaphore dsp_mutex;
 
+static int sleeps = 0; /* default is not to sleep for hi-sample rate sounds 
*/
+
+MODULE_PARM(sleeps, "i");
+
 typedef struct {
 	uint32_t cmd;		/* Command ID           */
 	uint32_t pos;		/* Sample position      */
@@ -341,7 +345,7 @@
 
 		for (i = 0; i < (HZ * 2); i++) {
 
-			if (chanh->freq < 23000)
+		  if ((chanh->freq < 23000)||(sleeps > 0))
 				interruptible_sleep_on_timeout(&
 							       (devc->
 								open_wait),
@@ -421,7 +425,7 @@
 {
 	int playpoint;
 	do {
-		if (chanh->freq < 23000)
+	  if (chanh->freq < 23000)
 			interruptible_sleep_on_timeout(&(devc->open_wait),
 						       1);
 		spu_write_wait();
@@ -432,7 +436,7 @@
 	if ((currentpoint + total_count) > 0x8000) {
 		currentpoint = 0;
 		do {
-			if (chanh->freq < 23000)
+		  if ((chanh->freq < 23000)||(sleeps > 0))
 				interruptible_sleep_on_timeout(&
 							       (devc->
 								open_wait),

[linuxdc-dev] Patch for aica sound driver

[Adrian M. <ad...@mc...>]

This patch should allow the aica module to be loaded with an option 'sleeps' 
parameter. With sleeps > 0 the module will sleep even for high sample sounds 
- so lessening the load. This may improve performance in some high stress 
environments.

The default behaviour (the only behaviour available when the code is built 
into the kernel) is for the code not to sleep, but to spin. This shoul 
guarantee high quality sound playback at the price of eating through cpu 
clock cycles.

The long term solution to this problem/choice may be for HZ to be set to a 
higher value (as proposed for 2.5 and optionally backported for 2.4) - ie to 
give the kernel a time granularity an order of magnitude smaller than now. 

I imagine a 200 MIPS machine like the DC should be able to handle that - any 
comemnts?


--- main.c	Fri Oct 18 21:05:18 2002
+++ linux-sh-dc/drivers/sound/aica/main.c	Fri Oct 18 21:02:40 2002
@@ -68,6 +68,10 @@
 static int currentpoint;
 static struct semaphore dsp_mutex;
 
+static int sleeps = 0; /* default is not to sleep for hi-sample rate sounds 
*/
+
+MODULE_PARAM(sleeps, "i");
+
 typedef struct {
 	uint32_t cmd;		/* Command ID           */
 	uint32_t pos;		/* Sample position      */
@@ -341,7 +345,7 @@
 
 		for (i = 0; i < (HZ * 2); i++) {
 
-			if (chanh->freq < 23000)
+		  if ((chanh->freq < 23000)||(sleeps > 0))
 				interruptible_sleep_on_timeout(&
 							       (devc->
 								open_wait),
@@ -421,7 +425,7 @@
 {
 	int playpoint;
 	do {
-		if (chanh->freq < 23000)
+	  if (chanh->freq < 23000)
 			interruptible_sleep_on_timeout(&(devc->open_wait),
 						       1);
 		spu_write_wait();
@@ -432,7 +436,7 @@
 	if ((currentpoint + total_count) > 0x8000) {
 		currentpoint = 0;
 		do {
-			if (chanh->freq < 23000)
+		  if ((chanh->freq < 23000)||(sleeps > 0))
 				interruptible_sleep_on_timeout(&
 							       (devc->
 								open_wait),

Re: [linuxdc-dev] Fwd: Kernel building

[Adrian M. <ad...@mc...>]

On Friday 18 Oct 2002 7:06 pm, Adrian McMenamin wrote:

>
> Hi... good morning, or maybe it's good evening for you.
>
>     My keyboard and VGA converters are late getting to me.  It's difficult
> to get a good idea of what's really running on the system without them.  I
> can however build and boot CDs.  I have problems in that area.  I can build
> Bill Gatliff's distribution with no problem.  Burns OK and boots up. Now I
> want to be able to build using the latest releases from the CVS tree so
> that I can use the new drivers (microphone, etc).  What I did is as
> follows: 1.. Build Bill's toolchain, kernel, initial RD just like
> instructed 2.. Burn Bill's image just to test it
>   3.. Download a stock 2.4.18 kernel
>   4.. Download CVS linuxSH kernel patches labeled linux-2.4-branch
>   5.. Perform treelink.sh using LinuxSH tree
>   6.. Perform treelink.sh using linux-dc tree
>   7.. Copied .config from Bill's distribution as a template.  I've also
> used other people's .config file with no luck. 

8.. Symbolically link my
> newly downloaded, patched tree into Bill's tree.  (linked 'kernel' to the
> source tree) 

Eh? You don't need to do this. A stock 2.4.18 kernel and the Linux-sh-dc and 
linux-sh modules are all you need.


9.. AN IMPORTANT DIFFERENCE?? - I have to modify the Makefile
> in kernel/arch/sh to remove the "-mnoimplicit-fp" switch since Bill's
> toolchain is a little old 10.. Did a make clean dep zImage
>   11.. Followed the normal steps I take making Bill's CD (compress initrd,
>  scramble image, etc..) 12.. Burn CD
>   13.. Boot in DC.  I get the initial Logo, SEGA splash screen.  And then
> the system resets itself.
>
> So what could I be doing wrong?  Do you have a similar set up?
> Perhaps my down-rev toolchain is causing some problems?
> I have a hard time believing that the CVS tree for linux-dc has problems.
>  Any help you can lend would be greatly appreciated.  If you think it's a
>  good idea, I can put this one out to the mailing list and see if anyone
> else has had this problem.
>
> Thanks
> Mike
> (anyone wanna buy a coaster??)
>
> -------------------------------------------------------
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev

[linuxdc-dev] Fwd: Kernel building

[Adrian M. <ad...@mc...>]

----------  Forwarded Message  ----------

Subject: Kernel building
Date: Fri, 18 Oct 2002 07:51:27 -0700
From: "Mike Barnett" <mik...@ho...>
To: <ad...@mc...>

Hi... good morning, or maybe it's good evening for you.

    My keyboard and VGA converters are late getting to me.  It's difficult to
 get a good idea of what's really running on the system without them.  I can
 however build and boot CDs.  I have problems in that area.  I can build Bill
 Gatliff's distribution with no problem.  Burns OK and boots up. Now I want
 to be able to build using the latest releases from the CVS tree so that I
 can use the new drivers (microphone, etc).  What I did is as follows: 1..
 Build Bill's toolchain, kernel, initial RD just like instructed 2.. Burn
 Bill's image just to test it
  3.. Download a stock 2.4.18 kernel
  4.. Download CVS linuxSH kernel patches labeled linux-2.4-branch
  5.. Perform treelink.sh using LinuxSH tree
  6.. Perform treelink.sh using linux-dc tree
  7.. Copied .config from Bill's distribution as a template.  I've also used
 other people's .config file with no luck. 8.. Symbolically link my newly
 downloaded, patched tree into Bill's tree.  (linked 'kernel' to the source
 tree) 9.. AN IMPORTANT DIFFERENCE?? - I have to modify the Makefile in
 kernel/arch/sh to remove the "-mnoimplicit-fp" switch since Bill's toolchain
 is a little old 10.. Did a make clean dep zImage
  11.. Followed the normal steps I take making Bill's CD (compress initrd,
 scramble image, etc..) 12.. Burn CD
  13.. Boot in DC.  I get the initial Logo, SEGA splash screen.  And then the
 system resets itself.

So what could I be doing wrong?  Do you have a similar set up?
Perhaps my down-rev toolchain is causing some problems?
I have a hard time believing that the CVS tree for linux-dc has problems. 
 Any help you can lend would be greatly appreciated.  If you think it's a
 good idea, I can put this one out to the mailing list and see if anyone else
 has had this problem.

Thanks
Mike
(anyone wanna buy a coaster??)

-------------------------------------------------------

Re: [linuxdc-dev] Looking to help out

[Adrian M. <ad...@mc...>]

Subject: Re: [linuxdc-dev] Looking to help out
Date: Mon, 14 Oct 2002 19:44:15 +0100
From: Adrian McMenamin <ad...@mc...>
To: "Mike Barnett" <mik...@ho...>

On Monday 14 Oct 2002 5:21 pm, Mike Barnett wrote:
> Hi
>     I'm just getting started with my dreamcast.  I've built both Bill's
> distribution as well as the Debian port.  Haven't been able to get a build
> from scratch to boot yet, it just resets my DC after the Sega splash
> screen.  I've seen messages in the archives where other's have had the same
> problem.  Once I get that solved, I'll be on my way to doing something
> productive.

Have you got a BBA or a coders' cable? One or the other is pretty much
essential if you are going to do something other than press coasters for the
rest of your life.

>     So, what's a productive thing to do to help the cause?  I'm a good
> embedded systems developer with lots of years under my belt, but am new at
> this Linux stuff.  I would like to work on a driver project (or a part of
> one) that's not too difficult.  Anyone have suggestions as to where I can
> lend a hand once I get a good build environment up and running?

Well, the main next thing is video, I suppose. Video support isn't brill at
the moment and much much more could be done - but I am not sure that is a
good place to start :->

I have always wanted a UK keyboard driver :-> There is broken microphone code
and only partially working puru puru pack code in the cvs courtesy of yours
truly - they could be fixed.

Or you could write code for the vmu/vms screen.

Adrian

> -Mike

-------------------------------------------------------