headers
Ruben Faelens | 1 May 2006 13:13
Picon

Re: Isl3893-devel digest, Vol 1 #130 - 3 msgs

Ericandor,

Here's a log from the booting process of my PA-RISC machine. Maybe it 
will help diagnosing your problems...

--------------
My dhcpd.conf:
--------------
allow bootp;
default-lease-time 600;
max-lease-time 7200;
ddns-update-style none;

subnet 10.91.10.0 netmask 255.255.255.0 {
}

host hppa-ruben {
         hardware ethernet 08:00:09:c5:cc:9c;
         fixed-address 10.91.10.70;
         filename "netboot.hppa";
}

******** in.tftpd is started like this:
in.tftpd -s -v /tftproot

******** A log from ethereal:
-- THE BOOTP REQUEST --
No.     Time        Source                Destination           Protocol 
Info
       4 45.369937   0.0.0.0               255.255.255.255       BOOTP
(Continue reading)

Permalink | Reply | 1 comment |
headers
Geert Stappers | 1 May 2006 18:59
Picon
Favicon

Re: some network files ...

On Mon, May 01, 2006 at 01:13:24PM +0200, Ruben Faelens wrote:
> Ericandor,
> 
> Here's a log from the booting process of my PA-RISC machine. Maybe it 
> will help diagnosing your problems...

Maybe, Maybe not ...

> --------------
> My dhcpd.conf:
> --------------
> allow bootp;
> default-lease-time 600;
> max-lease-time 7200;
> ddns-update-style none;
> 
> subnet 10.91.10.0 netmask 255.255.255.0 {

n.n.10.o

> }
> 
> host hppa-ruben {
>         hardware ethernet 08:00:09:c5:cc:9c;
>         fixed-address 10.91.10.70;

n.n.10.o

>         filename "netboot.hppa";
> }
(Continue reading)

Permalink | Reply | 0 comments |
headers
Arco | 26 May 2006 14:51
Picon

other kernels

Did anyone tried another kernel version on a isl3893?
(and did you succeed?)

Arco

-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
Permalink | Reply | 0 comments |
headers
Ruben Faelens | 27 May 2006 16:22
Picon

Re: other kernels

Arno,

The thing is, that there are a number of adjustments needed to make 
uClinux run succesfully on the isl3893. We have tried to extract these 
adjustments from the isl3893-SDK, but they have used an unofficial 
version of uClinux (extracted from CVS) to build their SDK. This makes 
comparing the SDK to an official uClinux version a time-consuming task. 
Unless someone figures out the patches needed to run a recent version of 
uClinux on isl3893, this will most likely not happen.

Ruben

-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642
Permalink | Reply | 3 comments |
headers
Arco | 27 May 2006 16:50
Picon

Re: Re: other kernels

I don't know what is essensial about the kernel (beside the drivers).
But if a new kernel only boots and has the serial console working it could be usefull.

There are a few parts I think that would be needed to make it usable:
- serial_isil
- the ethernet driver

When compiling 2.4.31 I get some errors but they not seem related to the serial driver.
Would it be usefull if I can create a memory map and connection scheme of my ap600?

On the other hand, why not use the existing kernel and use a new userspace? (which requires a
vendor/Intersil in uClinux)

Arco

Ruben Faelens wrote ..
> Arno, s/n/c/
> 
> The thing is, that there are a number of adjustments needed to make 
> uClinux run succesfully on the isl3893. We have tried to extract these
> adjustments from the isl3893-SDK, but they have used an unofficial 
> version of uClinux (extracted from CVS) to build their SDK. This makes
> comparing the SDK to an official uClinux version a time-consuming task.
> Unless someone figures out the patches needed to run a recent version of
> uClinux on isl3893, this will most likely not happen.
> 
> Ruben
> 
> 
> -------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Erich Schubert | 27 May 2006 17:03
Picon
Favicon

Re: Re: other kernels

Hi,
> version of uClinux (extracted from CVS) to build their SDK. This makes 
> comparing the SDK to an official uClinux version a time-consuming task. 
> Unless someone figures out the patches needed to run a recent version of 
> uClinux on isl3893, this will most likely not happen.

I don't think it's that bad, actually. I once found out which uclinux
kernel
they used as a base and ran a diff against that, which was just 180k.
That's a manageab size, actually. You can get it here:
http://isl3893.sourceforge.net/download/patches/diff-uclinux-2.4.19-uc1-to-intersil.diff

If you want to port that to a newer kernel, leave all the MPU stuff away
at first... you can run it with the MPU disabled, and it will still
work, you just won't have the little bit of memory-protection the MPU
can do.

It's just that someone needs to actually DO it. Split that diff into
separate chunks and apply them to a current uclinux branch.

Just like apparently noone cared about the memory-management fix I
posted here some months ago which will allow you to use SSL and SSH on
the box. Everbody is expecting someone else to do all the work and come
out with a Debian-like SDK for this box, so all you need to do is
"apt-get install oepnvpn" and you have openvpn running on the box... but
that is not the way Opensource works, sorry.

best regards,
Erich Schubert
--

--
(Continue reading)

Permalink | Reply | 2 comments |
headers
Arco | 27 May 2006 17:59
Picon

Splitting the Diff

I'm a bit afraid of diffs I have to admit:
 kernel-decompose is the isl-flavour?
 + needs to be added
 - is removed (so has to be a check so the original can stay)
 what do I do with the "Only in kernel-decompose" parts?

Arco

#------8<-----------------------------
put this script and diff-uclinux-2.4.19-uc1-to-intersil.diff in a temp directory, now we have about 92
parts 8-)

# cat split.sh
mkdir -p output
rm output/*.diff 2>/dev/null
awk 'BEGIN {file="start.diff"; }
/^diff/ {file=$4;
        gsub(/\//,"_",file);
        gsub(/\./,"_",file);
        gsub(/__/,"",file);
        gsub(/$/,".diff",file);
        gsub(/^/,"output/",file);
        }
// { print >> file }
'  diff-uclinux-2.4.19-uc1-to-intersil.diff
#------8<-----------------------------

Erich Schubert wrote ..
> I don't think it's that bad, actually. I once found out which uclinux
> kernel
(Continue reading)

Permalink | Reply | 501 comments |
headers
Erich Schubert | 27 May 2006 19:08
Picon
Favicon

Re: Splitting the Diff

Hi Arco,
> I'm a bit afraid of diffs I have to admit:
>  kernel-decompose is the isl-flavour?

I don't remember. Should be obvious from the changes.

>  what do I do with the "Only in kernel-decompose" parts?

That means the file wasn't present in the other tree. Grab the whole
file from the corresponsing kernel source tree.

I don't think you should automatically split the file.
Often changes to one file belong to different changesets.

Note that diffutils contains lots of tools to work on diffs - interdiff
and such things.

So I'd basically go through the 180k diff file "one hunk at a time", and
apply them to a CVS checkout of the official kernel source, trying to do
only one feature addition at a time. Whenever something seems to be
complete, run "cvs diff" to get a clean diff vs. the original cvs tree.

Maybe even work with multiple checkouts,
- uclinux unmodified upstream
- with isl3893 cpu patches added
- with bzip2 image compression support
- ...

So apply the hunks into different "branches". Then try to make them
compile cleanly next...
(Continue reading)

Permalink | Reply | 501 comments |
headers
Erich Schubert | 29 May 2006 20:38
Picon
Favicon

[Fwd: SourceForge.net Support: Over-quota notice for project: isl3893]

FYI:
SOMEONE needs to take care of this ASAP.
I have absolutely no time for handling it. I don't know what happens if
we don't react, if they're going to kill some files or so?

And honestly, I don't care. I guess I'll resign from the project.

-------- Weitergeleitete Nachricht --------
> Betreff: SourceForge.net Support: Over-quota notice for project:
> isl3893
[...]
> You are receiving this message as your SourceForge.net project,
> isl3893, is currently over its quota in its project group directory
> located on the SourceForge.net shell server. Your project has a 100000 k
> soft quota and your project is currently using 352412 k of disk. This new
> quota system allows us to track quotas granted to projects. Follow the
> instructions below to request a quota increase for your project to stop
> future mailings like this one from being sent to your project. The
> following command can be run at any time on the project shell server to
> check your project's disk usage:
> 
> du -skx /home/groups/i/is/isl3893/
> 
> Please take action to reduce your project's disk usage as soon as
> reasonably possible, but no later than 2006-06-05. For your quick reference, you
> may access your user home directory using any SSH client:
> 
> Host: shell.sourceforge.net
> Home Directory: /home/groups/i/is/isl3893/
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Roland Mieslinger | 29 May 2006 22:24
Picon
Picon

Re: [Fwd: SourceForge.net Support: Over-quota notice for project: isl3893]

Hi,

I'd recommend to delete the following files/dir:

tmp/Software 77664k  seems to be an unpacked firmeware
sdk-beta-2   14756k  same files with same size as in tmp

This files sum up to 192095k
htdocs/download/routers/linksys-wet54gv2/src/wet54gv2_2.07.tgz
htdocs/download/routers/siemens-wlanap600rp/src/AP-600RP_GNU_source-code.zip
htdocs/download/sdk/XG1100_2000GPL.zip
htdocs/download/toolchain/isl3893-stripped-toolchain.tgz

total sum of all is 284515k (we are 252412k over quota)

I suggest to remove the files on Friday, to give everyone a last change
to make a private copy.

Roland

On Mon, 2006-05-29 at 20:38 +0200, Erich Schubert wrote:
> FYI:
> SOMEONE needs to take care of this ASAP.
> I have absolutely no time for handling it. I don't know what happens if
> we don't react, if they're going to kill some files or so?
> 
> And honestly, I don't care. I guess I'll resign from the project.

-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
(Continue reading)

Permalink | Reply | 0 comments |

Gmane