Re: Applying patches.

mind entropy wrote:
> On Mon, May 13, 2013 at 4:05 PM, Juergen Beisert <jbe@...> wrote:
>> mind entropy wrote:
>>> [...]
>>>
>>>> Did you use my BSP or do you try to build your own kernel?
>>>
>>> I trying to apply your patches to the vanilla kernel. I am using
>>> emdebian rootfs. I have booted the vanilla kernel minus the patches on
>>> to the mini2440 board. Now I want to try with just your kernel patches.
>>
>> Then you should skip the stable patches and only use the Mini2440 related
>> in the list.
>
> That means the files ending with name patches? There are a lot of diff's in
> the directory too in
> 
OSELAS.BSP-Pengutronix-Mini2440/configs/platform-friendlyarm-mini2440/patches/linux-3.9

You should take a look into the "series" file, then you will see, what patches 
are stable patches and what patches are (still) relevant for the Mini2440.

> Also are these patches getting merged into mainline?

No. These are platform patches, and they become obsolete when the ARM 
architecture is fully switched to device tree description. I think in one or 
two kernel releases I can remove them entirely. Until then they are still 
needed.

Regards,

Re: Applying patches.

Hi,

mind entropy wrote:
>   I have downloaded the bsp from git (http://git-public.pengutronix.de/). I
> want to patch the linux3.9.1 vanilla kernel and took the patch-3.9.1.bz2
> from  OSELAS.BSP-Pengutronix-Mini2440/configs/platform-friendlyarm-mini2440/patches/linux-3.9.
>
>  I put the patch before the kernel source tree and did patch -p1 <
> ../patch-3.9.1 to the linux3.9.1 kernel but I get
>
> patching file Makefile
> Reversed (or previously applied) patch detected!  Assume -R? [n]
>
> and the patching fails. How should I patch this to the vanilla kernel?

The 'patch-3.9.1.bz2' is dedicated to patch the *3.9.0* kernel to become a
3.9.1 kernel.
If you start with a *3.9.1* kernel all these patches from the
'patch-3.9.1.bz2' archive are already present in the source tree. That is the
meaning of the "Reversed (or previously applied) patch detected!" message.

Regards,
Juergen

--

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

Applying patches.

How to change on the kernel the Pinmux in phyCORE-AM335x-PD12.1.0

Hi,

I would like change the pin configuration in the u-boot for the phyCORE-AM335x before I have changed the pin
configuration in the User's space with debugfs. I have already the headers from pinmux application
(mux.h and pinmux.h), but the issue is when I changed the files in the u-boot source:

-----
~/u-boot-2011.09/board/logicpd/am3517evm.h ---(here I changed that header to include the new pinmux.h)
~/u-boot-2011.09/arch/arm/include/asm/arch-omap3--(here I change the old mux.h for the new mux.h)

Then I make a drop to the u-boot and barebox to recopile the new u-boot with this custom configuration. Once I
update the barebox and the MLO in the board, I realize that the pin configuration still the same, Perhaps I
change the incorrect mux.h and pinmux.h for the new ones but I don't know where the file, that I have to
change, is.

-Regards

Breixo

compiig libXt - use local headers

How to active timer 2 in AM335x Linux 3.2

Hi,
The same question in a plane text, sorry for the problems was caused

I would like to have access to the Reg CLKSEL_TIMER_CLK (phy add: 0x44E00508) in the User space because I am
trying to active the Mux of the timer with selection3 (timer 2= 32 kHz). I have already a Kernel with debugfs
active, but when I mount debugfs I don't manage to find this register. I have been working with a Linux
kernel 3.2 with the Preempt Patch for OSALD  (Linux 3.2.40-rt60) in a PhyCORE-AM335x board.

I also tried to work /sys/devices/system/cpu/cpu0 but with any successful.

Any help would be grateful,

-Regards

Breixo Lopez Garcia

How to activ the Timer2 in AM335x Linux 3.2.40-rt60

Re: about mini6410

Hi Yi,

Yi Qingliang wrote:
> I'm working on mini6410, and can't boot from nand, I checked the barebox
> code, found there is no nand driver for 64xx, and no lowlevel_init.s, and
> searched google found: (maybe it is wrote by you, I'm not sure)

The Mini6410-BSP still comes with U-Boot. And U-Boot is able to boot from 
NAND, but from the older SLC types only. What kind of NAND do you are using?

> "The next release for the Mini6410 should be a real improvement. I'm
> working on a better bootloader (Barebox), but not finished yet. If you have
> a more recent working kernel for the Mini6410 I would be happy to include it
> into the BSP and do an interim release, just for a kernel update."
>
> what about current state? can barebox boot from nand on mini6410?

It is still in the same state when I wrote the sentence above. Sorry.

Regards
Juergen

--

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

building qemu for target

mini2440 kernel tries to revert to 2.6.39

After trying to do something exciting on the mini2440 and failing I did a
ptxdist clean kernel and ptxdist clean root.

On ptxdist go the first thing that happens is that is tries to download 2.6.39

The selected_platformconfig says:

PTXCONF_KERNEL_VERSION="3.7"

Before I clean everything out and start again, does this problem ring any bells?

Thanks,
Dave 

mini2440 kernel module development

Hi,

I have read through:

PTXdist Application Note
Kernel Driver Development

and it doesn't seem to apply to current versions of PTXdist.  Is there a
more recent App note?

Thanks,
Dave