for v4.1.
>
> A.
I would suggest to include at least patches 01, 04, 06. Probably
those could go to -stable tree... but this decision is up to you.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 07 March 2015 16:56:01 Grazvydas Ignotas wrote:
> N900's old board files specify 5030, but .dts does not.
I would guess this is bug and DTS file needs to be fixed.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Friday 06 March 2015 23:40:34 Pavel Machek wrote:
> On Sat 2015-03-07 00:12:07, Grazvydas Ignotas wrote:
> > On Fri, Mar 6, 2015 at 11:57 PM, Pali Rohár
> > wrote:
> > > On Friday 06 March 2015 22:24:17 Pavel Machek wrote:
> > >> Hi!
> > >>
On Friday 06 March 2015 22:24:17 Pavel Machek wrote:
> Hi!
>
> According to n900 dts, twl4030-bci (aka charger) should be
> included.
>
AFAIK it is not present on n900...
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Friday 06 March 2015 19:36:32 Tony Lindgren wrote:
> * Pali Rohár [150226 05:54]:
> > This patch series fix crypto support for omap3 devices which
> > use DT.
> >
> > It enables AES and SHAM on N9/N950 and SHAM on N900. AES is
> > still disabled for N900.
&g
On Monday 02 March 2015 21:51:48 Sebastian Reichel wrote:
> Hi,
>
> On Mon, Mar 02, 2015 at 08:05:31PM +0100, Pali Rohár wrote:
> > On Monday 02 March 2015 05:38:50 Sebastian Reichel wrote:
> > > This patchset contains the missing speech data support for
&g
l.h
Hello, do you have also DT patches? Or no DT changes are needed?
Is this cmt_speech version one from linux-n900 git tree? or it is
new or modified?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
cmfw.bin
>
> Best regards,
> Pavel
>
Do you have userspace application for initializing mac address?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Friday 27 February 2015 16:43:20 Tony Lindgren wrote:
> * Pali Rohár [150226 05:54]:
> > Harmattan system on Nokia N9 and N950 devices uses omap
> > crypto support. Bootloader on those devices is known that
> > it enables HW crypto support. This patch just include
>
On Thursday 26 February 2015 23:46:05 Aaro Koskinen wrote:
> Hi,
>
> On Thu, Feb 26, 2015 at 02:49:50PM +0100, Pali Rohár wrote:
> > This patch series fix crypto support for omap3 devices which
> > use DT.
> >
> > It enables AES and SHAM on N9/N950 and SHAM on N9
Register crypto hwmod links only if they are not disabled in DT.
If DT information is missing, enable them only for GP devices.
Before this patch crypto hwmod links were always disabled for all HS devices
and it was not possible to use omap-aes and omap-sham linux drivers.
Signed-off-by: Pali
omap3 support is same as omap2, just with different IO address (specified in DT)
Signed-off-by: Pali Rohár
---
drivers/crypto/omap-sham.c |4
1 file changed, 4 insertions(+)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
index 3c76696..b20e374 100644
--- a
Without this patch function pm_runtime_get_sync() returns 0 even when some
omap subfunction fails. This patch properly propagate error codes from omap
functions back to caller.
This patch fix problem, when loading omap-aes driver in qemu cause kernel oops.
Signed-off-by: Pali Rohár
---
arch
This patch adds missing dma DTS definitions for omap aes and sham drivers.
Without it kernel drivers do not work.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap3.dtsi |4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/omap3.dtsi b/arch/arm/boot/dts/omap3.dtsi
Harmattan system on Nokia N9 and N950 devices uses omap crypto support.
Bootloader on those devices is known that it enables HW crypto support.
This patch just include omap36xx.dtsi directly, so aes and sham is enabled.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap3-n950-n9.dtsi |2
This patch just move content of file omap34xx-hs.dtsi into omap3-tao3530.dts.
There is no code change, patch is just preparation for removing -hs file.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap3-tao3530.dtsi | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff
Function pm_runtime_get_sync could fail and we need to check return
value to prevent kernel crash.
Signed-off-by: Pali Rohár
---
drivers/crypto/omap-sham.c |9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/crypto/omap-sham.c b/drivers/crypto/omap-sham.c
official bootloader and crypto
enable bootloader. So we can safely enable sham code.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap3-n900.dts | 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
Device timer12 is automatically disabled on all HS devices via DTS property
"ti,timer-secure" in file omap3.dtsi so it can be safely removed. We do not
need to disable it on another place.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap34xx-hs.dtsi |4
arch/arm/boot/dt
These files are not used by any DTS file anymore.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap34xx-hs.dtsi | 12
arch/arm/boot/dts/omap36xx-hs.dtsi | 12
2 files changed, 24 deletions(-)
delete mode 100644 arch/arm/boot/dts/omap34xx-hs.dtsi
delete mode
This patch series fix crypto support for omap3 devices which use DT.
It enables AES and SHAM on N9/N950 and SHAM on N900. AES is still disabled for
N900.
Pali Rohár (10):
ARM: OMAP2+: Return correct error values from device and hwmod
ARM: OMAP3: Fix crypto support for HS devices
crypto
On Wednesday 25 February 2015 10:50:00 Pavel Machek wrote:
> On Tue 2015-02-24 09:37:34, Tony Lindgren wrote:
> > * Pali Rohár [150224 09:42]:
> > > On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
> > > > * Pali Rohár [150218 16:03]:
>
On Tuesday 24 February 2015 18:37:34 Tony Lindgren wrote:
> * Pali Rohár [150224 09:42]:
> > On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
> > > * Pali Rohár [150218 16:03]:
> > > > --- a/arch/arm/mach-omap2/omap_hwmod_3xxx_data.c
>
On Tuesday 24 February 2015 18:25:12 Tony Lindgren wrote:
> * Pali Rohár [150218 16:03]:
> > On Wednesday 18 February 2015 22:02:30 Pali Rohár wrote:
> > > On Wednesday 18 February 2015 13:21:03 Pali Rohár wrote:
> > > > Hello,
> > > >
> > > &
On Friday 20 February 2015 10:24:35 Arnd Bergmann wrote:
> On Thursday 19 February 2015 17:49:50 Pali Rohár wrote:
> > Offset for smc91x must be zero otherwise smc91x linux kernel
> > driver does not detect smc91x ethernet hardware in qemu
> > N900 machine.
> >
&g
On Friday 20 February 2015 09:22:26 Pavel Machek wrote:
> On Fri 2015-02-20 00:41:41, Pali Rohár wrote:
> > Without this patch function pm_runtime_get_sync() returns 0
> > even when some omap subfunction fails. This patch properly
> > propagate error codes from omap fun
On Wednesday 18 February 2015 22:36:41 Pali Rohár wrote:
> On Monday 09 February 2015 12:25:00 Pali Rohár wrote:
> > On Saturday 31 January 2015 16:29:36 Pali Rohár wrote:
> > > Hello,
> > >
> > > when I enable problematic omap_aes.ko driver (also in DT)
>
Without this patch function pm_runtime_get_sync() returns 0 even when some
omap subfunction fails. This patch properly propagate error codes from omap
functions back to caller.
This patch fix problem, when loading omap-aes driver in qemu cause kernel oops.
Signed-off-by: Pali Rohár
---
arch
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
> On 11 February 2015 at 13:39, Pali Rohár wrote:
> >> Anyhow, since checking the firewalls/APs to see if you have
> >> permission will probably only get you yet another fault if
> >> things are walled
Offset for smc91x must be zero otherwise smc91x linux kernel driver does not
detect smc91x ethernet hardware in qemu N900 machine.
Signed-off-by: Pali Rohár
---
arch/arm/boot/dts/omap3-n900.dts |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap3-n900
On Wednesday 18 February 2015 23:42:06 Tony Lindgren wrote:
> * Pali Rohár [150218 11:07]:
> > On Wednesday 18 February 2015 17:33:53 Tony Lindgren wrote:
> > > > */ +// reg = <1 0x300 0xf>;/* 16 byte IO range at
> >
> > offset
> &
On Thursday 19 February 2015 05:50:48 Tony Lindgren wrote:
> * Pali Rohár [150218 15:58]:
> > On Wednesday 18 February 2015 23:42:06 Tony Lindgren wrote:
> > > Of course it's always possible to do do a
> > > omap3-n900-qemu.dts if larger changes are needed :)
>
On Wednesday 18 February 2015 23:42:06 Tony Lindgren wrote:
> * Pali Rohár [150218 11:07]:
> > On Wednesday 18 February 2015 17:33:53 Tony Lindgren wrote:
> > > > */ +// reg = <1 0x300 0xf>;/* 16 byte IO range
at
> >
> > offset
> &
On Monday 09 February 2015 12:25:00 Pali Rohár wrote:
> On Saturday 31 January 2015 16:29:36 Pali Rohár wrote:
> > Hello,
> >
> > when I enable problematic omap_aes.ko driver (also in DT)
> > for Nokia N900 machine in qemu (it emulates OMAP GP device,
> > not HS)
On Wednesday 18 February 2015 22:02:30 Pali Rohár wrote:
> On Wednesday 18 February 2015 13:21:03 Pali Rohár wrote:
> > Hello,
> >
> > I tried to test OMAP AES driver on Nokia N900 with special
> > Nokia bootloader which enable L3 firewall for OMAP AES HW
> > supp
On Wednesday 11 February 2015 21:40:33 Nishanth Menon wrote:
> On Wed, Feb 11, 2015 at 2:28 PM, Pali Rohár
wrote:
> > On Wednesday 11 February 2015 16:22:51 Matthijs van Duin
wrote:
> >> On 11 February 2015 at 13:39, Pali Rohár
> >>
> >
> > wrote:
>
On Wednesday 18 February 2015 13:21:03 Pali Rohár wrote:
> Hello,
>
> I tried to test OMAP AES driver on Nokia N900 with special
> Nokia bootloader which enable L3 firewall for OMAP AES HW
> support.
>
> I modified arch/arm/boot/dts/omap34xx-hs.dtsi file and
> commente
On Wednesday 18 February 2015 17:33:53 Tony Lindgren wrote:
> * Pali Rohár [150218 07:23]:
> > On Tuesday 06 January 2015 00:02:29 Tony Lindgren wrote:
> > > Revert "ARM: dts: Disable smc91x on n900 until bootloader
> > > dependency is removed". We'
et eth0: Ethernet addr: 52:54:00:12:34:56
[ 20.624938] smc91x 200.ethernet eth0: No PHY found
(and eth0 exists in ifconfig)
If I do not apply my patch I got this error message:
[ 22.134704] smc91x 2000300.ethernet (unnamed net_device) (uninitialized):
smc91x: bank signature probe
missing in DT or in hwmod?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Sunday 15 February 2015 17:20:29 Pavel Machek wrote:
> On Sun 2015-02-15 12:08:02, Pali Rohár wrote:
> > On Sunday 15 February 2015 11:21:52 Pavel Machek wrote:
> > > Hi!
> > >
> > > By default, output goes to loudspeaker (top right relative
> > >
nels and settings for different profiles.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Wednesday 11 February 2015 21:43:42 Pavel Machek wrote:
> Hi!
>
> On Sun 2015-02-01 09:56:28, Pali Rohár wrote:
> > On Sunday 01 February 2015 02:36:06 Matthijs van Duin wrote:
> > > On 31 January 2015 at 20:06, Pali Rohár
> > >
> > >
> > >
On Wednesday 11 February 2015 16:22:51 Matthijs van Duin wrote:
> On 11 February 2015 at 13:39, Pali Rohár
wrote:
> >> Anyhow, since checking the firewalls/APs to see if you have
> >> permission will probably only get you yet another fault if
> >> things are walled
On Saturday 31 January 2015 16:13:39 Matthijs van Duin wrote:
> On 31 January 2015 at 12:34, Pali Rohár
wrote:
> > [ 172.923553] Unhandled fault: external abort on
> > non-linefetch (0x1018) at 0xb6f87028 [ 172.930664] In-band
> > Error seen by MPU at address 0
>
>
ne_initcall+0x98/0x140)
> > (kernel_init_freeable+0x16c/0x23c)
> > (kernel_init+0x8/0x100)
> > (ret_from_fork+0x14/0x3c)
> > Code: e1811002 e5932020 e590300c e0833002 (e593c000)
Sebastian,
can you try to add #define DEBUG into drivers/crypto/omap-aes.c,
enable AES in n900 DT and provide full dmesg output (with kernel
crash) which occur on your device? I think you get that previous
output from serial console, right? Also your compiled omap-aes.ko
module (with debug symbols) and your modified source code could
help.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 31 January 2015 16:29:36 Pali Rohár wrote:
> Hello,
>
> when I enable problematic omap_aes.ko driver (also in DT) for
> Nokia N900 machine in qemu (it emulates OMAP GP device, not
> HS) I get this error message in dmesg at modprobe time:
>
> [ 37.660339] -
ases become i2c0, i2c1
> and i2c2. Fix that by providing the correct aliases in the
> board dts.
>
> Signed-off-by: Ivaylo Dimitrov
> ---
> arch/arm/boot/dts/omap3-n900.dts | 7 +++
> 1 file changed, 7 insertions(+)
>
Works fine,
Tested-by: Pali Rohár
--
P
On Monday 02 February 2015 23:27:27 Felipe Balbi wrote:
> On Mon, Feb 02, 2015 at 04:17:13PM -0600, Felipe Balbi wrote:
> > On Sat, Jan 31, 2015 at 10:25:09AM +0100, Pali Rohár wrote:
> > > On Saturday 31 January 2015 10:06:11 Pali Rohár wrote:
> > > > Hello,
devices. It comes from some EEPROM memory stored in N900
and without HW hacking it is not possible to rewrite.
I would suggest to add support for bq27x00_battery module to do
not report design capacity. Maybe in N900 DT file can be property
which tell driver to ignore it.
> messages, that&#x
On Sunday 01 February 2015 02:36:06 Matthijs van Duin wrote:
> On 31 January 2015 at 20:06, Pali Rohár
> wrote:
> > I have configured two testing N900 devices. One with signed
> > bootloader which enable omap aes support and one device with
> > signed bootloader which
figured in the
> L4-Core AP (2KB @ 0x4804), and since they have an
> integrated memory map you'd automatically know which entry is
> responsible, assuming you can access the AP at all.
Do you have idea if it is possible to write such check in kernel
if address (aes@480c5000) is readable or not?
I have configured two testing N900 devices. One with signed
bootloader which enable omap aes support and one device with
signed bootloader which does not enable omap aes support.
So I can run any code/kernel patch and compare results/dumps
between those two devices.
Just I do not know what to do, or what to test...
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 31 January 2015 16:13:39 Matthijs van Duin wrote:
> On 31 January 2015 at 12:34, Pali Rohár
wrote:
> > [ 172.923553] Unhandled fault: external abort on
> > non-linefetch (0x1018) at 0xb6f87028 [ 172.930664] In-band
> > Error seen by MPU at address 0
>
>
DMA. It is for OMAP GP device (but emulated), so can TI comment
this problem (as this is not HS under NDA)?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 17 January 2015 18:41:26 Tony Lindgren wrote:
> * Pali Rohár [150117 09:32]:
> > On Saturday 17 January 2015 18:04:11 Tony Lindgren wrote:
> > > * Pali Rohár [150117 01:21]:
> > > > Hello, after playing with aes and non-aes version of
> > > &g
On Saturday 31 January 2015 12:11:30 Aaro Koskinen wrote:
> Hi,
>
> On Sat, Jan 31, 2015 at 12:08:31PM +0100, Pali Rohár wrote:
> > On Saturday 31 January 2015 12:05:09 Aaro Koskinen wrote:
> > > Hi,
> > >
> > > On Sat, Jan 31, 2015 at 10:28:46AM +0100,
On Saturday 31 January 2015 12:05:09 Aaro Koskinen wrote:
> Hi,
>
> On Sat, Jan 31, 2015 at 10:28:46AM +0100, Pali Rohár wrote:
> > when I boot 3.19 kernel on real n900 device it show these
> > errors in dmesg:
> >
> > [0.256103] hw-breakpoint: debug
fails to initialize?
I applied also these patches:
https://lkml.org/lkml/2015/1/29/465
http://mailman.alsa-project.org/pipermail/alsa-devel/2015-January/087228.html
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 31 January 2015 10:06:11 Pali Rohár wrote:
> Hello,
>
> when I try to modprobe g_nokia.ko gadget module on n900
> device, it produce tons on lines to display and then crash
> and reboot device. So its not working and I (without Nokia
> (TM) serial console I cannot
Hello,
when I try to modprobe g_nokia.ko gadget module on n900 device,
it produce tons on lines to display and then crash and reboot
device. So its not working and I (without Nokia (TM) serial
console I cannot debug it).
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is
357c2d2 100644
> > --- a/sound/soc/omap/rx51.c
> > +++ b/sound/soc/omap/rx51.c
> > @@ -250,14 +250,14 @@ static const struct snd_soc_dapm_route
> > audio_map[] = {
> >
> > {"FM Transmitter", NULL, "LLOUT"},
> > {"FM Transmitte
ls on DT kernel.
Reason is because I have another non-mainline driver which is
using GPIOs and in non DT kernel is initialized *after* audio.
And in DT kernel is initialized *before* audio.
Once I changed my non-mainline driver to not request av jack
gpio, rx51-audio driver loads fine in qemu.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
ore robust
solution:
> > Tested-by: Pavel Machek
> >
> > (Note, that in 3.19 dts for n900 got too big, so we are
> > actually triggering old bugs. That means that this is a
> > regression fix, and should go in ASAP).
>
> It is queued here:
> http://www.arm.linu
On Tuesday 27 January 2015 14:41:43 Peter Ujfalusi wrote:
> On 01/27/2015 03:32 PM, Pavel Machek wrote:
> > On Tue 2015-01-27 15:27:58, Peter Ujfalusi wrote:
> >> Hi,
> >>
> >> On 01/26/2015 10:51 PM, Pali Rohár wrote:
> >>> qemu does not emulate it
qemu does not emulate it
Signed-off-by: Pali Rohár
---
sound/soc/omap/rx51.c | 45 +
1 file changed, 25 insertions(+), 20 deletions(-)
diff --git a/sound/soc/omap/rx51.c b/sound/soc/omap/rx51.c
index 04896d6..a689021 100644
--- a/sound/soc/omap
On Monday 26 January 2015 17:14:55 Tony Lindgren wrote:
> * Pali Rohár [150123 14:39]:
> > On Friday 23 January 2015 22:39:55 Pali Rohár wrote:
> > > Hello,
> > >
> > > when I boot zImage with appended DT n900 in qemu
> > > fdt_open_into() function ca
On Saturday 24 January 2015 23:08:00 Arnd Bergmann wrote:
> On Saturday 24 January 2015 13:00:00 Pali Rohár wrote:
> > Another regression for DT setup (which does not occur for
> > board code):
> >
> > omap_hsmmc driver does not export slot_name sysfs entry
> > b
On Wednesday 26 November 2014 16:27:57 Pali Rohár wrote:
> On Wednesday 26 November 2014 16:22:00 Pavel Machek wrote:
> > On Wed 2014-11-26 14:36:42, Pali Rohár wrote:
> > > On Wednesday 26 November 2014 14:28:01 Pavel Machek wrote:
> > > > Hi!
> > > >
host/omap_hsmmc.c
@@ -2021,6 +2021,8 @@ static struct omap_hsmmc_platform_data
*of_get_hsmmc_pdata(struct device *dev)
if (of_find_property(np, "enable-sdio-wakeup", NULL))
pdata->pm_caps |= MMC_PM_WAKE_SDIO_IRQ;
+ of_property_read_string(np, "slot-name", &pdata->name);
+
return pdata;
}
#else
With this patch identification works fine:
/ # cat /sys/block/mmcblk0/device/../slot_name
external
/ # cat /sys/block/mmcblk1/device/../slot_name
internal
Without patch omap_hsmmc driver does not create slot_name.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
he thing to do would be to compare the register
> output between the two different firmware versions.
>
> Regards,
>
> Tony
Joel Fernandes, you are author of omap-des driver. Do you know
something about crashing kernel when omap crypto support (via L3
firewall) is not enabled
On Saturday 24 January 2015 00:48:55 Pavel Machek wrote:
> On Fri 2015-01-23 23:36:36, Pali Rohár wrote:
> > On Friday 23 January 2015 22:39:55 Pali Rohár wrote:
> > > Hello,
> > >
> > > when I boot zImage with appended DT n900 in qemu
> > > fdt_ope
On Friday 23 January 2015 22:39:55 Pali Rohár wrote:
> Hello,
>
> when I boot zImage with appended DT n900 in qemu
> fdt_open_into() function called from file
> arch/arm/boot/compressed/atags_to_fdt.c (in function
> atags_to_fdt) always returns -FDT_ERR_NOSPACE.
>
>
real n900 device I see that booted DT version also ignore
cmdline arguments from bootloader. I cannot debug decompress code
on real device, but I think it is same problem as in qemu.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Friday 23 January 2015 18:20:12 Guenter Roeck wrote:
> On Fri, Jan 23, 2015 at 02:15:56PM +0100, Pali Rohár wrote:
> > Hello,
>
> > I'm getting these two errors when booting DT linux v3.19-rc5
in n900 qemu:
> Hello Pali,
>
> can you send me the kernel confgura
.739776] [] (kthread) from []
(ret_from_fork+0x14/0x3c)
[0.740173] ---[ end trace 172dd94cb4e47d45 ]---
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
g to RFC2822 specification must be
delimited by CRLF. Maybe this is reason?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Saturday 17 January 2015 18:04:11 Tony Lindgren wrote:
> * Pali Rohár [150117 01:21]:
> > Hello, after playing with aes and non-aes version of
> > bootloaders I found out that code which configure L3
> > firewall must be in signed X-Loader part. So probably we
> >
On Wednesday 26 November 2014 18:54:12 Tony Lindgren wrote:
> * Pali Rohár [141125 13:33]:
> > On Tuesday 25 November 2014 22:08:17 Pali Rohár wrote:
> > > On Sunday 08 December 2013 00:22:06 Tony Lindgren wrote:
> > > > * Sebastian Reichel [131207 15:04]:
> >
issues to drop n900 legacy booting.
>
> If people have the boards listed above, please pitch in to do
> the .dts files or send the boards to me and I can do minimal
> .dts files for them.
>
> Regards,
>
> Tony
CCing Pavel Machek
He reported also some (still not fixed) regressions on n900.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
9] Loading kernel image info
Loading kernel (202 kB)... done in 27 ms (7457 kB/s)
[ 0.202] Loading initfs image info
[ 0.203] Total bootup time 286 ms
[ 0.206] Serial console enabled
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
h ethtool from Linux,
> > something like this:
> >
> > Run u-boot/tools/gen_eth_addr to generate a random local
> > mac, then swap the bytes for it for big endian. Enter them
> > into a file with hexedit in big endian order. Then just do:
> >
> > # cat mac | ethtool -E eth0 offset 0x40 length 6
> >
> > Then ethtool -e eth0 should show you the configuration.
>
> Oh and I have some u-boot patches that I'll post that allow
> booting n900 with bootz and to use smsc91x tftp booting. I'll
> try to post those shortly..
>
> Regards,
>
> Tony
N900 uboot support is broken, see my email on uboot ML with
bisected commits:
http://lists.denx.de/pipermail/u-boot/2015-January/200154.html
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
ormal n900.
>
> Tested-by: Aaro Koskinen
>
> I also tested with a development board, eth0 seemed to appear,
> but couldn't configure the MAC address with busybox ifconfig.
> How should it be done, I guess the interface does not have any
> MAC by default?
>
> A.
Should not kernel generate some random mac address if driver does
not provide one?
You can try to set (temporary) mac address to if with ifconfig:
$ ifconfig eth0 hw ether
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Tuesday 06 January 2015 16:03:54 Sebastian Reichel wrote:
> Hi Pali,
>
> On Tue, Jan 06, 2015 at 12:09:15AM +0100, Pali Rohár wrote:
> > Just to note that smc91x ethernet support is also in qemu
> > n900 emulation. Later I will try if it work with upstream
> > kerne
t;;
> interrupts = <22 IRQ_TYPE_LEVEL_HIGH>; /* gpio54 */
> reg = <1 0x300 0xf>;/* 16 byte IO range at offset
0x300
> */
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
rch/arm/mach-omap2/control.h"
> >
> > No need to do this, you can use syscon here like
> > pbias-regulator.c is doing.
>
> Oh looks like you're already using syscon, nice. What defines
> do you need from control.h?
>
> Those should be in the driver
el) without U-Boot. After NOLO load & boot kernel I
do not see any other output from serial console. Also on qemu
screen there is no new output (just NOKIA logo from bootloader).
I do not have this problem when doing legacy/board code boot with
3.19-rc1 kernel, so this problem is rel
is some unhandled iir value in function
static irqreturn_t hci_h4p_interrupt(int irq, void *data)
which cause that driver is not working?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
vert the patch.
>
> That is good news, because reverting it on 3.18-rcX brings h4p
> back, too (and as machine boots on nfsroot, debugging should
> be possible.)
>
> Best regards,
> Pavel
Reverted in l
vert the patch.
>
> That is good news, because reverting it on 3.18-rcX brings h4p
> back, too (and as machine boots on nfsroot, debugging should
> be possible.)
>
> Best regards,
> Pavel
Hi! this
On Saturday 06 December 2014 19:04:29 Pavel Machek wrote:
> On Sat 2014-12-06 18:40:16, Pali Rohár wrote:
> > On Saturday 06 December 2014 18:35:27 Pavel Machek wrote:
> > > Hi!
> > >
> > > For a long time, MMC was not working during boot...
> > >
irst time ... in a long time.
>
Hi, do you mean external SD card or internal eMMC (MyDocs)?
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Thursday 04 December 2014 19:40:34 Tony Lindgren wrote:
> * Pali Rohár [141204 10:36]:
> > see last mail in thread (I CCed you):
> > "[PATCH] ARM: /proc/cpuinfo: Use DT machine name when
> > possible"
> >
> > There is already some layer f
On Friday 28 November 2014 23:24:26 Tony Lindgren wrote:
> * Pali Rohár [141128 13:43]:
> > On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> > > Are you saying there are some issues with that?
> >
> > uboot (in mode when is loaded from NOLO) has those is
On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> * Pali Rohár [141127 03:34]:
> > On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> > > Thinking about this probably the best long term solution
> > > is to pass optional board_revision in the kerne
On Friday 28 November 2014 23:41:35 Aaro Koskinen wrote:
> Hi,
>
> On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> > uboot (in mode when is loaded from NOLO) has those issues:
> >
> > 1) uboot cannot read n900 onenand mtd (uboot onenand driver
>
On Friday 28 November 2014 23:26:30 Aaro Koskinen wrote:
> Hi,
>
> On Fri, Nov 28, 2014 at 10:41:12PM +0100, Pali Rohár wrote:
> > Does kernel provide some interface for telling userspace
> > applications something like bootreason (e.g power key,
> > software reset, r
On Friday 28 November 2014 23:24:26 Tony Lindgren wrote:
> * Pali Rohár [141128 13:43]:
> > On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> > > Are you saying there are some issues with that?
> >
> > uboot (in mode when is loaded from NOLO) has those is
On Friday 28 November 2014 21:27:19 Tony Lindgren wrote:
> * Pali Rohár [141127 03:34]:
> > On Thursday 27 November 2014 02:12:04 Tony Lindgren wrote:
> > > Thinking about this probably the best long term solution
> > > is to pass optional board_revision in the kerne
why we have different gpio in board data and
in DTS data? I'm sure that isp1704 worked from legacy board data
without problem, so I do not understand why in DTS code is
different gpio number.
--
Pali Rohár
pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
101 - 200 of 349 matches
Mail list logo
