All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi <opencode@gmx.net>
To: David Daney <ddaney@avtrex.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Problems booting Linux kernel on Sigma SMP8634 #2
Date: Wed, 05 Mar 2008 19:25:16 +0100	[thread overview]
Message-ID: <47CEE58C.7020507@gmx.net> (raw)
In-Reply-To: <47CED252.20800@avtrex.com>

Hi,

> I build and successfully run kernels on the 8634 every day, so I don't
> think it is a problem with the 8634 port in general.
> 
> You should probably ask for technical support from whomever supplied
> your hardware.  They would know the technical details about how to
> configure the memory controller, the amount and location of the RAM on
> the board, etc.

Thats right. And I would really like to do so. But unfortunately there
is not much information around about the hardware. Since the box
originally runs a wince system, this project is more like a _free time_
projects of some Linux enthusiasts.

You can get a overview about this here: http://www.t-hack.com/wiki/
There is also a forum, but unfortunately most posts are in German ..

>> I am sure there some more guys around using the smp8634.
> 
> Likely there are.  It is used in many blu-ray disk players, among other
> things.

Ok, there is not much information about the smp8634 out there, which is
really a pity. I know that Sigma is not really interested in publishing
there specifications. Even the gpl part is not published, but I am sure
you already know this :-)

Do you know how to get some more detailed information about the smp8634?

Ok, there are some parts that are not equal, like memory and flash! But
this is a SoC, so most parts are the same.


> N/A, the kernel does not rely on any microcode.

Ok, thanks, so we can cancel this on our todo-list ..



Regards,
	Andi

  reply	other threads:[~2008-03-05 18:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05 12:35 Problems booting Linux kernel on Sigma SMP8634 #2 Andi
2008-03-05 17:03 ` David Daney
2008-03-05 18:25   ` Andi [this message]
2008-03-13 10:11     ` Andi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47CEE58C.7020507@gmx.net \
    --to=opencode@gmx.net \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.