Hi Geert,
I've stuck a copy of the OpenPIC PDF at:
http://www.printk.net/pub/docs/openpic/
If AMD or anyone else objects then I'll take it down - I don't see why
they'd care about it - but since it's not listed anywhere else and the
guy we met from AMD thought it would be alright. Sometime soon
Have you turned on emulation of FP in the kernel?
- kumar
On Oct 13, 2004, at 4:01 PM, Dan Malek wrote:
>
>
> On Oct 13, 2004, at 1:07 PM, Laurent Lagrange wrote:
>
> > The console is mapped on SCC1 port.
> > CCSRBAR is mapped at 0xF800 and immr at 0xF808.
>
> I would suggest using the
In message <20041013193959.57540.qmail at web15605.mail.cnb.yahoo.com> you
wrote:
>
> I'd like to make sure about the meaning of BSP and
> LSP. There is sth unclear in my mind, I am afraid.
Don't worry. These terms are not clearly defined at all.
> IMHO, BSP includes Board's Hardware Scheme and
Hai anamayya,
I need to port linux to PowerPC based Board?
Could you give me some specific information about this?
For example, which embedded linux kernel (not commercial) is good for
this job?
Regards,
Mukund jampala
The attached script (wrapper/setup to crosstool.sh) gets me
a toolchain sufficient to build the default-config ppc kernel
(2.6.8.1, NPTL, gcc-3.4.2, glibc-2.3.3).
It tweaks the patch Dan references below for a ppc-ism,
then adds a patch (thanks Google!) to mask an issue that
gcc-3.4.2 has with inl
0 0 7 1 6 (L-TLB)
[c0004510] [c000bf8c] [c00de400] [c00042b8]
??? nothing more ???
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20041013/174442a4/attachment.htm
On Tue, Oct 12, 2004 at 04:34:32PM -0700, Eugene Surovegin wrote:
> On Wed, Oct 13, 2004 at 12:03:21AM +0100, Jon Masters wrote:
> > On Tue, 12 Oct 2004 14:36:34 -0700, Eugene Surovegin
> > wrote:
> >
> > > Did you use ioremap to get valid kernel virtual address for your
> > > device registers?
On Oct 13, 2004, at 5:23 PM, annamaya wrote:
> I verified that the TX and RX clock signals are
> correct and the CMXFCR route register is programmed
> correctly for FCC2. I still see TX timeout errors. I
> am stumped. :-(
Do you have the FCC MAC set up properly for
full or half duplex? If you d
> I was talking about the trademark infringement. You are talking about
> something completely different,
Well, actually I was talking about both issues, but here's what I think
about Philips patenting i2c: It's great work if you can get it.
And I think I'm going to wrap it up for the day, a
On Wed, 13 Oct 2004, Eugene Surovegin wrote:
> Yeah, the most "extreme" variant being "two-wire serial interface",
> without even mentioning I2C or IIC.
>
> You need some familiarity with bus protocol to figure out that this is
> really I2C :).
oh, gawd, i'm sorry i started this. :-P
rday
On Oct 13, 2004, at 3:21 PM, annamaya wrote:
> I looked at the driver again and it looks like the TX
> and RX clock signals are board specific. I will also
> have to program the CMXFCR clock route register with
> the appropriate clocks. Am I on the right track here?
Yep. :-)
-- Dan
On Oct 13, 2004, at 1:07 PM, Laurent Lagrange wrote:
> The console is mapped on SCC1 port.
> CCSRBAR is mapped at 0xF800 and immr at 0xF808.
I would suggest using the standard memory map the rest of
us use for 8560. It makes the porting lots easier.
> I open 2 TLBs on memory and a big
> On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote:
> > Just to mess with your minds... I2C is a trademark of Philips
> > Electronics N.V. so that is probably not the best choice from a
> > legalistic point of view.
>
> It's been related to me several times that this is th
the available Embedded Linux ports for PowerPC?
Regards,
Mukund jampala
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20041013/504314d2/attachment.htm
On Wed, 13 Oct 2004, Eugene Surovegin wrote:
> On Wed, Oct 13, 2004 at 02:26:23PM -0400, Robert P. J. Day wrote:
> >
> > i was just about to rename some of my variables and macros to be
> > consistent with what i *thought* was the standard nomenclature of
> > "IIC" as opposed to "I2C". just che
On Wed, 13 Oct 2004, Mark Chambers wrote:
> - Original Message -
> From: "Robert P. J. Day"
> To: "Embedded PPC Linux list"
> Sent: Wednesday, October 13, 2004 2:26 PM
> Subject: "I2C" versus "IIC"
>
> My vote, since nobody asked, would be "I2C". I've always heard people
> say "I square
- Original Message -
From: "Robert P. J. Day" <[EMAIL PROTECTED]>
To: "Embedded PPC Linux list"
Sent: Wednesday, October 13, 2004 2:26 PM
Subject: "I2C" versus "IIC"
My vote, since nobody asked, would be "I2C". I've always heard people
say "I squared C", and since only CBS can get super
i was just about to rename some of my variables and macros to be
consistent with what i *thought* was the standard nomenclature of
"IIC" as opposed to "I2C". just checked include/asm-ppc, and grepped
for case-insensitive instances of both strings ... oh, god. there's
really no preferred usage,
I verified that the TX and RX clock signals are
correct and the CMXFCR route register is programmed
correctly for FCC2. I still see TX timeout errors. I
am stumped. :-(
--- Dan Malek wrote:
>
> On Oct 13, 2004, at 3:21 PM, annamaya wrote:
>
> > I looked at the driver again and it looks like th
On Wed, Oct 13, 2004 at 02:14:28PM -0700, Eugene Surovegin wrote:
> On Wed, Oct 13, 2004 at 01:26:13PM -0700, Matt Porter wrote:
> > On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote:
> > > Just to mess with your minds... I2C is a trademark of Philips
> > > Electronics N.V. so
> -Original Message-
> From: linuxppc-embedded-bounces at ozlabs.org
> [mailto:linuxppc-embedded-bounces at ozlabs.org] On Behalf Of
> Eugene Surovegin
> Sent: Wednesday, October 13, 2004 3:34 PM
> To: Robert P. J. Day
> Cc: Embedded PPC Linux list
> Subject: Re: "I2C" versus "IIC"
>
> On
On Wed, Oct 13, 2004 at 01:26:13PM -0700, Matt Porter wrote:
> On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote:
> > Just to mess with your minds... I2C is a trademark of Philips
> > Electronics N.V. so that is probably not the best choice from a
> > legalistic point of view.
On Wed, Oct 13, 2004 at 01:54:44PM -0700, Matt Porter wrote:
> On Wed, Oct 13, 2004 at 04:48:34PM -0400, Mark Chambers wrote:
> >
> >
> > > On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote:
> > > > Just to mess with your minds... I2C is a trademark of Philips
> > > > Electr
Mukund JB. wrote:
> Hello all,
>
> This is my first visit to the mailists.
>
> I have assigned to port Embedded Linux to PowerPC Board.
>
>
>
> Where do I get the Embedded Linux kernel & Source code for PowerPC?
>
> Can you provide me with some documents related to porting Embedded Linux
>
On Wed, Oct 13, 2004 at 04:48:34PM -0400, Mark Chambers wrote:
>
>
> > On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote:
> > > Just to mess with your minds... I2C is a trademark of Philips
> > > Electronics N.V. so that is probably not the best choice from a
> > > legalisti
On Wed, Oct 13, 2004 at 02:18:03PM -0600, VanBaren, Gerald (AGRE) wrote:
> Just to mess with your minds... I2C is a trademark of Philips
> Electronics N.V. so that is probably not the best choice from a
> legalistic point of view.
It's been related to me several times that this is the reason why
m
On Wed, Oct 13, 2004 at 02:26:23PM -0400, Robert P. J. Day wrote:
>
> i was just about to rename some of my variables and macros to be
> consistent with what i *thought* was the standard nomenclature of
> "IIC" as opposed to "I2C". just checked include/asm-ppc, and grepped
> for case-insensitiv
I looked at the driver again and it looks like the TX
and RX clock signals are board specific. I will also
have to program the CMXFCR clock route register with
the appropriate clocks. Am I on the right track here?
--- annamaya wrote:
> I was able to use the same driver on a PQ2-FADS
> board
> wi
My vote is for I2C :-)
--- Mark Chambers wrote:
> - Original Message -
> From: "Robert P. J. Day"
> To: "Embedded PPC Linux list"
>
> Sent: Wednesday, October 13, 2004 2:26 PM
> Subject: "I2C" versus "IIC"
>
> My vote, since nobody asked, would be "I2C". I've
> always heard people
>
On Oct 13, 2004, at 10:49 AM, annamaya wrote:
> . But my driver doesn't work and complains
> about a TX timeout. I am sure I am missing something.
> Can you suggest something that I could try?
You are going to have to track down the clock and
control signals for the FCC and make sure they ar
I was able to use the same driver on a PQ2-FADS board
with an MPC8275 processor. Are you telling me that
some of these pins are board specific? Thanks for your
help.
--- Dan Malek wrote:
>
> On Oct 13, 2004, at 10:49 AM, annamaya wrote:
>
> > . But my driver doesn't work and complains
> >
So,
Is this patch available? Will it be available soon or applied to any ppc
kernel tree?
This is in my to-do list for the near future, so it would be very helpful if
this were already done.
Best regards,
Alex
> -Original Message-
> From: Dan Malek [SMTP:dan at embeddededge.com]
> Sent:
Thanks (After some days of holydays).
Now, promiscous mode works fine, so board is bridging ok.
Best regards,
Alex
-Original Message-
From: Rune Torgersen [SMTP:runet at innovsys.com]
Sent: Friday, October 08, 2004 4:02 PM
To: alebas at televes.com
Cc: linuxppc-embedded at
VanBaren has already answered your question in detail.
Use the Linux Kernel from www.denx.de and you should
be fine. Once you have the kernel, start looking into
the arch/ppc/ sub-directory and you will be able to
find all the stuff that you will need to port your new
board.
And which boot monito
Thanks for the reply Dan. Just before I got your mail,
I was going through the fcc ethernet driver from
mvista and I noticed the BCSR hack code to make the
PHY work on an EP8260. I went back to the manual for
the EP8280 and realized that they did something
similar on this board, just as you guessed
>
> From: linuxppc-embedded-bounces at ozlabs.org
[mailto:linuxppc-embedded-bounces at ozlabs.org] On Behalf Of Mukund JB.
> Sent: Wednesday, October 13, 2004 6:45 AM
> To: linuxppc-embedded at ozlabs.org
> Subject: Embedded linux port for PowerPC ?
>
> Hello all,
>
On Wed, 13 Oct 2004 00:03:21 +0100, Jon Masters wrote:
> Possibly also use io_block_mapping on ppc to map a block of IO memory
> before ioremapping.
Actually, in this case that's a bad idea. Ignore that.
Jon.
On Tue, 12 Oct 2004 14:36:34 -0700, Eugene Surovegin wrote:
> Did you use ioremap to get valid kernel virtual address for your
> device registers? You generally cannot just use physical address to
> access device from the device driver.
Possibly also use io_block_mapping on ppc to map a block of
38 matches
Mail list logo
