Anyone have the source code?

[A543]

We certainly could use a copy of the source code here.  Post it if you got it.

[AndyMan]

I'll second that...   Or a copy of the md5sum file (worth it's weigh in GOLD) if we can get a copy

I'll put the word out on some other forums I frequent... you never know

[A543]

The source code is available, you just need to request it, afaik. It falls under the GNU license or something like that so they have to make it available.  There's an obscure reference to sending a request for it hidden deep in their website I remember reading.

[sprockkets]

That be true, and that's the GPL license. If only they shared that mentality with their windows software... oh wait we have so much crap to protect; we want all the control, not for u!

[sbingner]

I have their 'source code' -- but all that is, is the kernel source...

[judb]

Interesting, I wonder if they use any other functions from say FLAC or one of the other popular encoders that has been modified in any way as they would need to distribute the source to that as well.

Can you post this code?  It would be interesting to try and see if we can use it to work in an emulator that was posted.

[A543]

I'm not sure how these licenses work so I'll ask the Linux gurus - if they are using two different versions of the kernel, RoyalLinux and Linux, then don't they have to supply both of those source codes?

[AndyMan]

I have their 'source code' -- but all that is, is the kernel source...

kernel source..?  would that be "royallin.ux" source, or "phatd" source?

[sbingner]

the source itself is pretty big... there are two makefiles, one makes the royallin.ux and the other makes the other one... it's just a different architecture.

README.PhatNoise follows:

Building for Phatnoise Car Audio System version 1.0 and 1.1.  

Environment:
A gcc 2.95.3 cross-compiler is needed.  arm-linux-gcc should be in your PATH.

You need to configure/build the kernels individually.  It is
unfortunately impossible to build one kernel which will work
on either board.  We screwed that one up.  

In other words, CONFIG_ARCH_PHATNOISE10 and
CONFIG_ARCH_PHATNOISE11 should be mutually exclusive.
CONFIG_ARCH_PHATNOISE should be defined in either case.  



Instructions:

1.  Copy either config.phatnoise10 or config.phatnoise11 to
a file named .config.  

2.  Run "make menuconfig".  Exit.  

3.  "make dep"

4.  "make"

You now have a file called "linux".  This is the binary kernel image
which gets loaded into memory by the boot loader.  On 1.0 boards,
you need to rename this file "RoyalLin.ux" because that is the file
name that the boot loader looks for.  On 1.1 boards, the file is named
"linux", but you also need a signature file called "linux.sig".



Cirrus Logic DAI Device Driver:

The driver is in the files linux/drivers/misc/cirrus_dai.c and
linux/drivers/misc/cirrus_dai_fiq.S (ARM assembly FIQ handler).




Brendan Dowling
Phatnoise, Inc.

[sbingner]

Hello Sam,

You may download the source code from this FTP site:

ftpup.phatnoise.com

username: ftpup
password: phatguest

The filename is phatlinux-for-V1.tar.bz2. Please note that this file is
rather
large (23MB). Please let us know if we may assist you further.

Best regards,

PhatNoise Customer Support

[AndyMan]

Sam, you seem to have a good raport with the guys there... have you tried asking how to make the sig file?

[sbingner]

lol, no I just submitted a bug asking for the source code and they sent me that... no way they would consider sending me something like that... even their own people don't have access to it by what I've seen.  They have a server that signs the files for their people

[AndyMan]

you never know... an "innocent" question to them (and throwing them a modified rc.sh) might just get us out of the doodoo if you know what I mean...

If they could get an RC.SH signed for us, we'd be golden

[A543]

Does this mean that the Red boxes load Royallin.ux and the rest only use Linux?
I should be able to delete Royallin.ux from my DMS then and all should be well. Correct?

[sbingner]

sure, but what would be the point?

Does this mean that the Red boxes load Royallin.ux and the rest only use Linux?
I should be able to delete Royallin.ux from my DMS then and all should be well. Correct?

[A543]

Also, see if there's anything else on that FTP site you could grab. You never know.

[para]

Nothing interesting apart from the sign script we already feature in this forum

BTW, we've to be careful not to violate any copyrights here. Posting non-public, non-GPL material might not be legal. Is this board considered public being open to anyone after registration?

Para

[sbingner]

Absolutely, which is why I haven't put up the binary for plsign anywhere

We're good posting info on how to modify the proprietary code as long as we don't include the code itself... should get this into the FAQ and as a banner on here

Nothing interesting apart from the sign script we already feature in this forum

BTW, we've to be careful not to violate any copyrights here. Posting non-public, non-GPL material might not be legal. Is this board considered public being open to anyone after registration?

Para

[A543]

sure, but what would be the point?

I'm just trying to focus on the boot order of the Phatbox. It was always possible that the first-boot processor loaded the unsigned kernel first, to handle the keycheck and firmware updates and then the ARM processor used the other kernel for regular operations.  But now we know.  Also, packing the files closer to the front of the disk with FAT systems makes for faster file access.  I know, I'm being anal.

[judb]

Well, I am curious about what boot loader they are using.  If the boot loader is looking for a signed drive somehow before loading the kernel that would have us pretty hosed.

Do we know where in the boot process the drive is being checked yet?

What might be useful would be to see if someone can get a dump of the ide bus during the boot process to see if we can figure out where this occurs.  I know someone out there can do it as that was how someone cracked the xbox a long time ago IIRC.