Tobias Klauser | 14 Jun 15:48 2011
Picon

Re: [PATCH v3 RESEND] watchdog: Add driver for Altera Watchdog Timer

Hi Wim

On 2011-05-27 at 10:23:09 +0200, Wim Van Sebroeck <wim@...> wrote:
> > This driver adds support for the Altera Timer in the Watchdog Timer
> > configuration. This component is usually found on SOPC (System on
> > Programmable Chip) for Altera FPGAs.
> > 
> > Signed-off-by: Tobias Klauser <tklauser@...>
> > Reviewed-by: Jamie Iles <jamie@...>
> > Acked-by: Grant Likely <grant.likely@...> (for the
devicetree binding)
> 
> Signed-off-by: Wim Van Sebroeck <wim@...>
> 
> I presume this will go in together with the other nios2 architecture patches?

It will probably take some time until we get to the point where we're
ready to submit nios2 arch patches. We started out with individual
drivers to get used to the submission and review process. Most of them
got taken by the respective subsystem maintainers.

So if you want to take the driver through your tree, please go ahead.
Otherwise I will resubmit it once we're ready to submit the nios2 arch.

Cheers
Tobias
Raphael Philipe | 17 Jun 14:55 2011
Picon

uClinux on Stratix III board

Hello Everyone,

This my first post in this mail list.

I'm a newbie on uClinux and I have some knowledge of Quartus and NIOS
II processor.

I'm trying to install uClinux on my stratix III dsp board. I want to
have access to some peripherals like ethernet and custom logic
components (not implemented yet).

The fact is that I'm facing problems compiling the newest version of
nios2-linux, described here
http://www.alterawiki.com/wiki/Creating_a_Nios_II_Design_with_an_MMU

I was able to compile, install and use the version 2.6.23 described
described here:
http://famschmid.net/uclinuxtutorial_nios.html

However, this version does not seem to have support to the triple
speed ethernet component (I think that the driver is only available in
the newer versions of nios-uClinux).

I used the hardware design available here:
http://www.alteraforum.com/forum/showthread.php?t=5886

Has someone compiled and Installed the newest version of uClinux on a
Stratix III board?  If so, can you give me some guidance? I would
appreciate that very much.

(Continue reading)

Caio | 17 Jun 15:17 2011
Picon

Re: uClinux on Stratix III board

Hello Raphael,

I work with Stratix II too, but I started with uClinux (MMU Less) ,
now my project use nios2-linux-20090730.tar version but now I'm having
some problems like a old kernel , old drivers(2.6.30), mainly by
jffs2/mtd driver's , but for to learning it's interesting.
The make vendor_hwselect SYSPTF=My_PROC.ptf it's a script for the
generate all the files of your board to kernel compile, this script
parse a ptf made some adjustment to start compile the kernel in high
level interface.

The sopc-create-header-files it's useful tool when you will build a
bootloader like u-boot to your board, for this you will need a .h
describing all the components and address of your board.

Best Regards,

Caio Pereira

2011/6/17 Raphael Philipe <rapphil@...>:
> Hello Everyone,
>
> This my first post in this mail list.
>
> I'm a newbie on uClinux and I have some knowledge of Quartus and NIOS
> II processor.
>
> I'm trying to install uClinux on my stratix III dsp board. I want to
> have access to some peripherals like ethernet and custom logic
> components (not implemented yet).
(Continue reading)

Raphael Philipe | 17 Jun 15:50 2011
Picon

Re: uClinux on Stratix III board

Actually I'm using one Stratix III board, not II.

But your information was worth.
Do you have any idea on how to compile with no MMU? I mean, what
version of gcc do I use to compile?
Thank you.

On Fri, Jun 17, 2011 at 10:17 AM, Caio <caiortp@...> wrote:
> Hello Raphael,
>
>
> I work with Stratix II too, but I started with uClinux (MMU Less) ,
> now my project use nios2-linux-20090730.tar version but now I'm having
> some problems like a old kernel , old drivers(2.6.30), mainly by
> jffs2/mtd driver's , but for to learning it's interesting.
> The make vendor_hwselect SYSPTF=My_PROC.ptf it's a script for the
> generate all the files of your board to kernel compile, this script
> parse a ptf made some adjustment to start compile the kernel in high
> level interface.
>
> The sopc-create-header-files it's useful tool when you will build a
> bootloader like u-boot to your board, for this you will need a .h
> describing all the components and address of your board.
>
> Best Regards,
>
> Caio Pereira
>
>
> 2011/6/17 Raphael Philipe <rapphil@...>:
(Continue reading)

Charlie Armijo | 17 Jun 17:09 2011
Picon

Re: uClinux on Stratix III board

Hi,

There are a couple of things to point out.
1. Nios uClinux (microC linux) is 
different from Nios Linux.  uClinux was the focal point of the Nios wiki. 
It was a well documented and organized website.

2. Nios uClinux does not support an MMU.

3. Nios Linux has both MMU and no MMU versions.

4. You need to make sure that you are not mixing up versions of the two 
operating systems.  To my knowledge the latest version of uClinux is 
2.6.30.  Linux is up to about 2.6.38.

5. Use "git clean -f -x -d" after updating to get rid of conflicts.

6. The current Altera wiki is extremely unorganized.  Instructions from 
the Nios Wiki for uClinux are side by side with the instructions for nios 
Linux.  Both use the directory uClinux-dist for the compilation of the 
respective kernels, which makes it difficult to determine what kernel 
system you are looking at.

7. Back about three years ago the way to tell the kernel about your board 
was to use:
vendor_hwselect SYSPTF=/absolute_path/my.ptf
uClinux still uses this.  However, I'm not sure how much longer Altera 
will support the .ptf file.

There was a migration to building header files using
(Continue reading)

Raphael Philipe | 17 Jun 17:43 2011
Picon

Re: uClinux on Stratix III board

Thank you Charlie. That was pretty clarifying.

I think that the explanations in the Altera Wiki are unorganized too.

In this case, I would like to try to use the Nios Linux with MMU support.
Sorry for my newbie,  but
 1 - Is possible to build a Nios Linux with MMU for my stratix III dev board?
 2 - If so, may I ask you what steps should I follow in order to learn
how to do it?

Thank you.

On Fri, Jun 17, 2011 at 12:09 PM, Charlie Armijo
<armijo@...> wrote:
> Hi,
>
> There are a couple of things to point out.
> 1. Nios uClinux (microC linux) is different from Nios Linux.  uClinux was
> the focal point of the Nios wiki. It was a well documented and organized
> website.
>
> 2. Nios uClinux does not support an MMU.
>
> 3. Nios Linux has both MMU and no MMU versions.
>
> 4. You need to make sure that you are not mixing up versions of the two
> operating systems.  To my knowledge the latest version of uClinux is 2.6.30.
>  Linux is up to about 2.6.38.
>
> 5. Use "git clean -f -x -d" after updating to get rid of conflicts.
(Continue reading)

Walter Goossens | 18 Jun 00:21 2011
Picon

Re: uClinux on Stratix III board

Hi Raphael,

To answer your first question: Yes.

NiosII and it's MMU is not really tied to a specific device/board as 
long as it's supported by Quartus and the device is large enough. I 
don't see any problems with either one of those on your board...

The second question is a bit harder to answer, but I'll have a stab at 
it anyway.
There are three components that need to be "made" and they all have 
choices :)
1 FPGA with Nios and (possibly) an MMU
2 a (uC)Linux kernel
3 some rootfs / userland software.

Okay, now for the choices:

1. FPGA image
You can create the FPGA using either sopc-builder or QSys. Most (all ?) 
tutorials on the net are based on sopc-builder so that might be a bit 
easier to get help with but either one is fine. If you want to go the 
mmu-less uCLinux way, I think your only option is sopc-builder because 
QSys doesn't generate PTF-files IIRC. See points 2 and 3 for other 
reasons why you would NOT want to choose that path anyway... If you're 
new to both sopc-builder and qsys then I'd suggest QSys since learning 
sopc-builder might be a bit like learning how to drive a steam-engine: 
Nice, but no real future (please no flamewars from steam-enthousiasts!).
The other choice is: Do I want an MMU?
Well, that all depends. If you want to run a "big" operating system such 
(Continue reading)

Tobias Klauser | 21 Jun 17:00 2011
Picon

Re: [PATCH] altera_tse: Remove obsolete third arg from interrupt handler

On Fri, 6 May 2011 16:41:06 +0100 Ian Abbott <abbotti@...> wrote:
> Interrupt handlers haven't had a 'struct pt_regs *' argument since
> 2.6.19.  Remove it.

Applied, thanks. And sorry for the delay.

Tobias
Tobias Klauser | 21 Jun 17:08 2011
Picon

Re: [PATCH] altera_tse: PHY_MAX_ADDR is not a valid PHY address

On Mon, 18 Apr 2011 14:11:18 +0100 Ian Abbott <abbotti@...> wrote:
> When the probe function reports available PHYs it starts at PHY_MAX_ADDR
> (0x20) and works its way down to 0 inclusive.  Since the PHY address is
> only 5 bits wide, then if there is a PHY at address 0, it gets reported
> twice - once at address 0x20 and once at address 0x0.  This bug is
> harmless.
> 
> The loop should count down from address PHY_MAX_ADDR - 1 (0x1F).

Applied as well, thanks.

Though I think we should get rid of this PHY reporting stuff all
together as this should already be handled by the PHY subsystem and the
user should query it there if needed.

Tobias
Tobias Klauser | 23 Jun 17:19 2011
Picon

Basic device tree support for altera_tse

Hi all

I just pushed initial device tree support for the altera_tse driver. It
still needs some manual tweaking of the dts to properly work, see the
commit message below.

Please test and let me know if it works for you. I'd also appreciate
comments on how to correctly get PHY interface mode
(PHY_INTERFACE_MODE_*) and supported modes (PHY_GBIT_FEATURES,
SUPPORTED_*) from device tree.

Cheers
Tobias

From c11184dc2edfb22227f31291e090dd3719fd2346 Mon Sep 17 00:00:00 2001
From: Tobias Klauser <klto@...>
Date: Thu, 23 Jun 2011 15:27:58 +0200
Subject: [PATCH 1/2] altera_tse: Add basic device tree support

As we thus can no longer rely on platform data (struct alt_tse_config),
we need to provide the information stored therein through other means.
The best solution I came up with was manually adding properties to the
dts file. Right now, these are the following two:

- ALTR,mii-id
- ALTR,phy-addr (optional, if not set PHY autodetection is used)

Also I hard-coded the PHY interface mode to PHY_INTERFACE_MODE_RGMII and
the supported modes for the PHY to PHY_GBIT_FEATURES. We will probably
need to figure out some way to properly provide this information through
(Continue reading)


Gmane