date:20131220

[linux-sunxi] Waiting for root device /dev/mmcblk0p2...

2013-12-20 Thread Puneet B

To boot android from sd card , i falllow this link

http://linux-sunxi.org/Boot_Android_from_SdCard

but it is booted up to kernel,

but file system is not booting.

Kindly tell me where i can indicate the file  system partition.

i am using android 4.2 (sun7i) source code.

here is my boot.cmd:

setenv console 'ttyS0,115200'
setenv root '/dev/mmcblk0p2'
setenv panicarg 'panic=10'
setenv extra 'rootfstype=ext4 rootwait'
setenv loglevel '8'
setenv setargs 'setenv bootargs console=${console} root=${root} 
loglevel=${loglevel} ${panicarg} ${extra}'
setenv kernel 'uImage'
setenv boot_mmc 'fatload mmc 0 0x4300 script.bin; fatload mmc 0 
0x4800 ${kernel}; bootm 0x4800'
setenv bootcmd 'run setargs boot_mmc'


Regards
Punith

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] mmc errors

2013-12-20 Thread Jonathan Aquilina

The problem is that boot up doesn't complete

On Friday 20 December 2013 20:25:25 Hans de Goede wrote:
> Hi,
> 
> On 12/20/2013 04:30 PM, Jonathan Aquilina wrote:
> > Hey guys I am getting these errors
> > 
> > <3>[mmc-err] smc 0 err, cmd 52,  RTO
> > [4.099702] [mmc-err] smc 0 err, cmd 52,  RTO
> > <3>[mmc-err] smc 0 err, cmd 52,  RTO
> > [4.108190] [mmc-err] smc 0 err, cmd 52,  RTO
> > <6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1
> > timing
> > LEGACY(SDR12) dt B
> > [4.120891] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V
> > width 1 timing LEGACY(SDR12) dt B
> > <6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1
> > timing
> > LEGACY(SDR12) dt B
> > [4.141002] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V
> > width 1 timing LEGACY(SDR12) dt B
> > <3>[mmc-err] smc 0 err, cmd 5,  RTO
> > [4.155772] [mmc-err] smc 0 err, cmd 5,  RTO
> > <3>[mmc-err] smc 0 err, cmd 5,  RTO
> > [4.164081] [mmc-err] smc 0 err, cmd 5,  RTO
> > <3>[mmc-err] smc 0 err, cmd 5,  RTO
> > [4.172399] [mmc-err] smc 0 err, cmd 5,  RTO
> > <3>[mmc-err] smc 0 err, cmd 5,  RTO
> > [4.180703] [mmc-err] smc 0 err, cmd 5,  RTO
> > <6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1
> > timing
> > LEGACY(SDR12) dt B
> > [4.193950] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V
> > width 1 timing LEGACY(SDR12) dt B
> > <6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1
> > timing
> > LEGACY(SDR12) dt B
> > [4.211685] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V
> > width 1 timing LEGACY(SDR12) dt B
> > <6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1
> > timing
> > LEGACY(SDR12) dt B
> > [4.231790] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V
> > width 1 timing LEGACY(SDR12) dt B
> > <3>[mmc-err] smc 0 err, cmd 2,  RTO
> > [4.247141] [mmc-err] smc 0 err, cmd 2,  RTO
> > <3>[mmc-err] smc 0 err, cmd 2,  RTO
> > [4.255473] [mmc-err] smc 0 err, cmd 2,  RTO
> > <3>[mmc-err] smc 0 err, cmd 2,  RTO
> > [4.263814] [mmc-err] smc 0 err, cmd 2,  RTO
> > <3>[mmc-err] smc 0 err, cmd 2,  RTO
> > [4.272123] [mmc-err] smc 0 err, cmd 2,  RTO
> > <3>mmc0: error -110 whilst initialising SD card
> > [4.280665] mmc0: error -110 whilst initialising SD card
> > <6>[mmc-msg] sdc0 set ios: clk 40Hz bm OD pm ON vdd 3.3V width 1
> > timing
> > LEGACY(SDR12) dt B
> > [4.294322] [mmc-msg] sdc0 set ios: clk 40Hz bm OD pm ON vdd 3.3V
> > width 1 timing LEGACY(SDR12) dt B
> > <3>[mmc-err] smc 0 err, cmd 1,  RTO
> > [4.307746] [mmc-err] smc 0 err, cmd 1,  RTO
> > <6>[mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing
> > LEGACY(SDR12) dt B
> > [4.320013] [mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width
> > 1 timing LEGACY(SDR12) dt B
> > <6>[mmc-msg] sdc0 power off
> > [4.331589] [mmc-msg] sdc0 power off
> > 
> > 
> > I am wondering what the issue is the memory card is not the issue at least
> > not on native linux on a non embedded system.
> 
> These errors are caused by the linux mmc subsystem making calls which only
> work on sdio devices (ie sdio wifi cards) which fail on sd-cards. This is
> only done during initial probing of the card when the mmc subsys tries to
> find out what kind of card is exactly connected. They can safely be
> ignored.
> 
> Regards,
> 
> 
> Hans

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Sun8i (A23) spotted in the wild.

2013-12-20 Thread Runzhong Yi

It could be possible since A23 can run as high as 1.8Ghz. If the core
run as 1650MHz then this mean the dram clock is 1/3 of the core clock.

2013/12/21 Patrick Wood :
> Am I reading the fex file correctly?  The DRAM is running at 552 MHz?
>
>
> On Friday, December 20, 2013 9:08:07 AM UTC-5, Luc Verhaegen wrote:
>>
>> On Thu, Dec 19, 2013 at 12:32:24AM +0100, Luc Verhaegen wrote:
>> > I tried to order myself one of those cheap Q88 tablets with an A13 just
>> > now. Big was my surprise when i got it and popped it open, as i was
>> > staring at an A23.
>> >
>> > Bad news all round really:
>> > * fully locked down android, no root, no adb. I will give another root
>> > exploit a try tomorrow.
>> > * our fel utility does not work.
>> > * we of course have no code for u-boot or linux yet.
>> > * nothing on the serial port.
>> >
>> > This device is a really serious GPL violator. They even went as far as
>> > removing all open source licenses from the About section under android
>> > settings.
>> >
>> > What we do know:
>> > * two obvious serial pads (which are not sending out anything atm)
>> > * it tries to boot off SD when a likely candidate is there
>> > * it has a 3.4.39 kernel, and the /proc/config.gz was world readable
>> > (this is where the string sun8i was found).
>> > * HW is an A23 which is a bga, with an AXP223 companion
>> >
>> > Board picture is available at the device page:
>> > http://linux-sunxi.org/Ippo_q8h
>> >
>> > Luc Verhaegen.
>>
>> In the meantime, adb access has been figured out and the device has been
>> rooted. All is documented on the page.
>>
>> script.bin has been fetched, and is available from:
>> http://dl.linux-sunxi.org/users/libv/ippo_q8h/
>>
>> Luc Verhaegen.
>
> --
> You received this message because you are subscribed to the Google Groups
> "linux-sunxi" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to linux-sunxi+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Maxime Ripard

Hi Hans,

On Fri, Dec 20, 2013 at 08:22:56PM +0100, Hans de Goede wrote:
> Hi,
> 
> On 12/20/2013 09:33 AM, Maxime Ripard wrote:
> >Hi Hans,
> >
> >On Fri, Dec 20, 2013 at 08:29:46AM +0100, Hans de Goede wrote:
> >>Hi,
> >>
> >>On 12/19/2013 10:49 PM, Юрий Пухальский wrote:
> >>>Good UTC night!
> >>>
> >>>
> >>>Got somewhat further, yet still there are problems.
> >>>Is there anything i should change in kernel cmdline maybe?
> >>
> >>Is this a sun5i device, iow A10s or A13 SOC based ? If so you
> >>need to build and boot with my sunxi-next u-boot branch:
> >>
> >>https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next
> >>
> >>The only time I've seen those clock update timeout errors is
> >>on sun5i with an unfixed uboot.
> >
> >It would be really great if it was to work without any changes in
> >u-boot.
> 
> I agree. For this to work we need to override the initial pll6
> frequency we inherit from u-boot, which for sun5i is 2400 MHz,
> which PLL6 can be configured to given its factors, but will not
> actually work at. I believe this is actually a broken
> power-on-reset value in PLL6-cfg, rather then u-boot's fault.
> 
> The problem is there is no clear / clean way to fix this in
> the suni-clk kernel code.

What did you think about/try ?

I think that adding a new factors calculation function for sun5i's
PLL6, that would limit the factors returned to whatever frequency is
adequate would work. Emilio?

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com


signature.asc
Description: Digital signature

[linux-sunxi] Re: [PATCH v4 2/2] ARM: sun4i/sun7i: RTC driver

2013-12-20 Thread Maxime Ripard

Hi Carlo,

On Mon, Dec 09, 2013 at 04:34:37PM +0100, Carlo Caione wrote:
> On Sat, Nov 16, 2013 at 6:33 PM, Carlo Caione  wrote:
> > This patch introduces the driver for the RTC in the Allwinner A10 and
> > A20 SoCs.
> >
> > Signed-off-by: Carlo Caione 
> > --
> > v3->v4:
> > - several bug fixes
> > - reworked for cycles
> > - implemented busy-waiting
> > - new macro for year offset
> > - new comments
> 
> Ping?

I just merged the two patches in the sunxi/drivers-for-3.14 branch.

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com


signature.asc
Description: Digital signature

[linux-sunxi] [PATCH 0/3] ARM: sunxi: Add A31 High Speed Timer Support

2013-12-20 Thread Maxime Ripard

Hi everyone,

This patchset enables support for the High Speed Timer IP found in the
Allwinner A31 SoCs.

These timers are asserted in reset, and are not associated with any struct
device, so we also add a small helper to the reset framework along the way to
be able to retrieve the reset controller from the device tree directly.

Thanks,
Maxime

Maxime Ripard (3):
  reset: Add of_reset_control_get
  clocksource: sun5i: Add support for reset controller
  ARM: sun6i: a31: Add support for the High Speed Timers

 .../bindings/timer/allwinner,sun5i-a13-hstimer.txt |  4 +++
 arch/arm/boot/dts/sun6i-a31.dtsi   | 11 ++
 drivers/clocksource/timer-sun5i.c  |  6 
 drivers/reset/core.c   | 39 +-
 include/linux/reset.h  |  4 +++
 5 files changed, 55 insertions(+), 9 deletions(-)

-- 
1.8.4.2

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] [PATCH 3/3] ARM: sun6i: a31: Add support for the High Speed Timers

2013-12-20 Thread Maxime Ripard

The Allwinner A31 has support for four high speed timers. Apart for the
number of timers (4 vs 2), it's basically the same logic than the high
speed timers found in the sun5i chips.

Now that we have a driver to support it, we can enable them in the
device tree.

Signed-off-by: Maxime Ripard 
---
 arch/arm/boot/dts/sun6i-a31.dtsi | 11 +++
 1 file changed, 11 insertions(+)

diff --git a/arch/arm/boot/dts/sun6i-a31.dtsi b/arch/arm/boot/dts/sun6i-a31.dtsi
index 5256ad9..9145c6d 100644
--- a/arch/arm/boot/dts/sun6i-a31.dtsi
+++ b/arch/arm/boot/dts/sun6i-a31.dtsi
@@ -312,6 +312,17 @@
status = "disabled";
};
 
+   hstimer@01c6 {
+   compatible = "allwinner,sun7i-a20-hstimer";
+   reg = <0x01c6 0x1000>;
+   interrupts = <0 51 4>,
+<0 52 4>,
+<0 53 4>,
+<0 54 4>;
+   clocks = <&ahb1_gates 19>;
+   resets = <&ahb1_rst 19>;
+   };
+
gic: interrupt-controller@01c81000 {
compatible = "arm,cortex-a7-gic", "arm,cortex-a15-gic";
reg = <0x01c81000 0x1000>,
-- 
1.8.4.2

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] [PATCH 2/3] clocksource: sun5i: Add support for reset controller

2013-12-20 Thread Maxime Ripard

The Allwinner A31 that uses this timer has the timer IP asserted in reset.
Add an optional reset property to the DT, and deassert the timer from reset if
it's there.

Signed-off-by: Maxime Ripard 
---
 .../devicetree/bindings/timer/allwinner,sun5i-a13-hstimer.txt   | 4 
 drivers/clocksource/timer-sun5i.c   | 6 ++
 2 files changed, 10 insertions(+)

diff --git 
a/Documentation/devicetree/bindings/timer/allwinner,sun5i-a13-hstimer.txt 
b/Documentation/devicetree/bindings/timer/allwinner,sun5i-a13-hstimer.txt
index 7c26154..27cfc7d 100644
--- a/Documentation/devicetree/bindings/timer/allwinner,sun5i-a13-hstimer.txt
+++ b/Documentation/devicetree/bindings/timer/allwinner,sun5i-a13-hstimer.txt
@@ -9,6 +9,9 @@ Required properties:
one)
 - clocks: phandle to the source clock (usually the AHB clock)
 
+Optionnal properties:
+- resets: phandle to a reset controller asserting the timer
+
 Example:
 
 timer@01c6 {
@@ -19,4 +22,5 @@ timer@01c6 {
 <0 53 1>,
 <0 54 1>;
clocks = <&ahb1_gates 19>;
+   resets = <&ahb1rst 19>;
 };
diff --git a/drivers/clocksource/timer-sun5i.c 
b/drivers/clocksource/timer-sun5i.c
index bddc522..f74d75e 100644
--- a/drivers/clocksource/timer-sun5i.c
+++ b/drivers/clocksource/timer-sun5i.c
@@ -16,6 +16,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
@@ -143,6 +144,7 @@ static u32 sun5i_timer_sched_read(void)
 
 static void __init sun5i_timer_init(struct device_node *node)
 {
+   struct reset_control *rstc;
unsigned long rate;
struct clk *clk;
int ret, irq;
@@ -162,6 +164,10 @@ static void __init sun5i_timer_init(struct device_node 
*node)
clk_prepare_enable(clk);
rate = clk_get_rate(clk);
 
+   rstc = of_reset_control_get(node, NULL);
+   if (!IS_ERR(rstc))
+   reset_control_deassert(rstc);
+
writel(~0, timer_base + TIMER_INTVAL_LO_REG(1));
writel(TIMER_CTL_ENABLE | TIMER_CTL_RELOAD,
   timer_base + TIMER_CTL_REG(1));
-- 
1.8.4.2

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] [PATCH 1/3] reset: Add of_reset_control_get

2013-12-20 Thread Maxime Ripard

In some cases, you might need to deassert from reset an hardware block that
doesn't associated to a struct device (CPUs, timers, etc.).

Add a small helper to retrieve the reset controller from the device tree
without the need to pass a struct device.

Signed-off-by: Maxime Ripard 
---
 drivers/reset/core.c  | 39 ++-
 include/linux/reset.h |  4 
 2 files changed, 34 insertions(+), 9 deletions(-)

diff --git a/drivers/reset/core.c b/drivers/reset/core.c
index d1b6089..4f3dda7 100644
--- a/drivers/reset/core.c
+++ b/drivers/reset/core.c
@@ -127,15 +127,16 @@ int reset_control_deassert(struct reset_control *rstc)
 EXPORT_SYMBOL_GPL(reset_control_deassert);
 
 /**
- * reset_control_get - Lookup and obtain a reference to a reset controller.
- * @dev: device to be reset by the controller
+ * of_reset_control_get - Lookup and obtain a reference to a reset controller.
+ * @node: device to be reset by the controller
  * @id: reset line name
  *
  * Returns a struct reset_control or IS_ERR() condition containing errno.
  *
  * Use of id names is optional.
  */
-struct reset_control *reset_control_get(struct device *dev, const char *id)
+struct reset_control *of_reset_control_get(struct device_node *node,
+  const char *id)
 {
struct reset_control *rstc = ERR_PTR(-EPROBE_DEFER);
struct reset_controller_dev *r, *rcdev;
@@ -144,13 +145,10 @@ struct reset_control *reset_control_get(struct device 
*dev, const char *id)
int rstc_id;
int ret;
 
-   if (!dev)
-   return ERR_PTR(-EINVAL);
-
if (id)
-   index = of_property_match_string(dev->of_node,
+   index = of_property_match_string(node,
 "reset-names", id);
-   ret = of_parse_phandle_with_args(dev->of_node, "resets", "#reset-cells",
+   ret = of_parse_phandle_with_args(node, "resets", "#reset-cells",
 index, &args);
if (ret)
return ERR_PTR(ret);
@@ -185,12 +183,35 @@ struct reset_control *reset_control_get(struct device 
*dev, const char *id)
return ERR_PTR(-ENOMEM);
}
 
-   rstc->dev = dev;
rstc->rcdev = rcdev;
rstc->id = rstc_id;
 
return rstc;
 }
+EXPORT_SYMBOL_GPL(of_reset_control_get);
+
+/**
+ * reset_control_get - Lookup and obtain a reference to a reset controller.
+ * @dev: device to be reset by the controller
+ * @id: reset line name
+ *
+ * Returns a struct reset_control or IS_ERR() condition containing errno.
+ *
+ * Use of id names is optional.
+ */
+struct reset_control *reset_control_get(struct device *dev, const char *id)
+{
+   struct reset_control *rstc;
+
+   if (!dev)
+   return ERR_PTR(-EINVAL);
+
+   rstc = of_reset_control_get(dev->of_node, id);
+   if (!IS_ERR(rstc))
+   rstc->dev = dev;
+
+   return rstc;
+}
 EXPORT_SYMBOL_GPL(reset_control_get);
 
 /**
diff --git a/include/linux/reset.h b/include/linux/reset.h
index 6082247..a398025 100644
--- a/include/linux/reset.h
+++ b/include/linux/reset.h
@@ -1,6 +1,8 @@
 #ifndef _LINUX_RESET_H_
 #define _LINUX_RESET_H_
 
+#include 
+
 struct device;
 struct reset_control;
 
@@ -8,6 +10,8 @@ int reset_control_reset(struct reset_control *rstc);
 int reset_control_assert(struct reset_control *rstc);
 int reset_control_deassert(struct reset_control *rstc);
 
+struct reset_control *of_reset_control_get(struct device_node *node,
+  const char *id);
 struct reset_control *reset_control_get(struct device *dev, const char *id);
 void reset_control_put(struct reset_control *rstc);
 struct reset_control *devm_reset_control_get(struct device *dev, const char 
*id);
-- 
1.8.4.2

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] mmc errors

2013-12-20 Thread Hans de Goede


Hi,

On 12/20/2013 04:30 PM, Jonathan Aquilina wrote:

Hey guys I am getting these errors

<3>[mmc-err] smc 0 err, cmd 52,  RTO
[4.099702] [mmc-err] smc 0 err, cmd 52,  RTO
<3>[mmc-err] smc 0 err, cmd 52,  RTO
[4.108190] [mmc-err] smc 0 err, cmd 52,  RTO
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.120891] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width
1 timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.141002] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width
1 timing LEGACY(SDR12) dt B
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.155772] [mmc-err] smc 0 err, cmd 5,  RTO
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.164081] [mmc-err] smc 0 err, cmd 5,  RTO
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.172399] [mmc-err] smc 0 err, cmd 5,  RTO
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.180703] [mmc-err] smc 0 err, cmd 5,  RTO
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.193950] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width
1 timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.211685] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width
1 timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.231790] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width
1 timing LEGACY(SDR12) dt B
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.247141] [mmc-err] smc 0 err, cmd 2,  RTO
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.255473] [mmc-err] smc 0 err, cmd 2,  RTO
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.263814] [mmc-err] smc 0 err, cmd 2,  RTO
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.272123] [mmc-err] smc 0 err, cmd 2,  RTO
<3>mmc0: error -110 whilst initialising SD card
[4.280665] mmc0: error -110 whilst initialising SD card
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm OD pm ON vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.294322] [mmc-msg] sdc0 set ios: clk 40Hz bm OD pm ON vdd 3.3V width
1 timing LEGACY(SDR12) dt B
<3>[mmc-err] smc 0 err, cmd 1,  RTO
[4.307746] [mmc-err] smc 0 err, cmd 1,  RTO
<6>[mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing
LEGACY(SDR12) dt B
[4.320013] [mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1
timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 power off
[4.331589] [mmc-msg] sdc0 power off


I am wondering what the issue is the memory card is not the issue at least not
on native linux on a non embedded system.


These errors are caused by the linux mmc subsystem making calls which only
work on sdio devices (ie sdio wifi cards) which fail on sd-cards. This is only 
done
during initial probing of the card when the mmc subsys tries to find out what 
kind
of card is exactly connected. They can safely be ignored.

Regards,


Hans


--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Hans de Goede


Hi,

On 12/20/2013 09:33 AM, Maxime Ripard wrote:

Hi Hans,

On Fri, Dec 20, 2013 at 08:29:46AM +0100, Hans de Goede wrote:

Hi,

On 12/19/2013 10:49 PM, Юрий Пухальский wrote:

Good UTC night!


Got somewhat further, yet still there are problems.
Is there anything i should change in kernel cmdline maybe?


Is this a sun5i device, iow A10s or A13 SOC based ? If so you
need to build and boot with my sunxi-next u-boot branch:

https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next

The only time I've seen those clock update timeout errors is
on sun5i with an unfixed uboot.


It would be really great if it was to work without any changes in
u-boot.


I agree. For this to work we need to override the initial pll6
frequency we inherit from u-boot, which for sun5i is 2400 MHz,
which PLL6 can be configured to given its factors, but will not
actually work at. I believe this is actually a broken
power-on-reset value in PLL6-cfg, rather then u-boot's fault.

The problem is there is no clear / clean way to fix this in
the suni-clk kernel code. So for now I've opted for a u-boot
patch since u-boot is already meddling with PLL-6 on sun4i and
sun7i, it seemed sensible to fix this up in u-boot for sun5i too.

As always I'm open to suggestions :)

Regards,

Hans

--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Sun8i (A23) spotted in the wild.

2013-12-20 Thread Patrick Wood

Am I reading the fex file correctly?  The DRAM is running at 552 MHz?

On Friday, December 20, 2013 9:08:07 AM UTC-5, Luc Verhaegen wrote:
>
> On Thu, Dec 19, 2013 at 12:32:24AM +0100, Luc Verhaegen wrote: 
> > I tried to order myself one of those cheap Q88 tablets with an A13 just 
> > now. Big was my surprise when i got it and popped it open, as i was 
> > staring at an A23. 
> > 
> > Bad news all round really: 
> > * fully locked down android, no root, no adb. I will give another root 
> > exploit a try tomorrow. 
> > * our fel utility does not work. 
> > * we of course have no code for u-boot or linux yet. 
> > * nothing on the serial port. 
> > 
> > This device is a really serious GPL violator. They even went as far as 
> > removing all open source licenses from the About section under android 
> > settings. 
> > 
> > What we do know: 
> > * two obvious serial pads (which are not sending out anything atm) 
> > * it tries to boot off SD when a likely candidate is there 
> > * it has a 3.4.39 kernel, and the /proc/config.gz was world readable 
> > (this is where the string sun8i was found). 
> > * HW is an A23 which is a bga, with an AXP223 companion 
> > 
> > Board picture is available at the device page: 
> > http://linux-sunxi.org/Ippo_q8h 
> > 
> > Luc Verhaegen. 
>
> In the meantime, adb access has been figured out and the device has been 
> rooted. All is documented on the page. 
>
> script.bin has been fetched, and is available from: 
> http://dl.linux-sunxi.org/users/libv/ippo_q8h/ 
>
> Luc Verhaegen. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Hans de Goede


Hi,

On 12/20/2013 11:28 AM, Юрий Пухальский wrote:

Oh, sorry. Silly me, i had dd'ed the uboot to wrong device =*)
Kernel started ok.
No VGA output, but probably it's as intended.


Right vga output is not supported with upstream kernels yet.

Regards,

Hans

--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] mmc errors

2013-12-20 Thread Jonathan Aquilina

Hey guys I am getting these errors

<3>[mmc-err] smc 0 err, cmd 52,  RTO
[4.099702] [mmc-err] smc 0 err, cmd 52,  RTO
<3>[mmc-err] smc 0 err, cmd 52,  RTO
[4.108190] [mmc-err] smc 0 err, cmd 52,  RTO
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.120891] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 
1 timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.141002] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 
1 timing LEGACY(SDR12) dt B
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.155772] [mmc-err] smc 0 err, cmd 5,  RTO
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.164081] [mmc-err] smc 0 err, cmd 5,  RTO
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.172399] [mmc-err] smc 0 err, cmd 5,  RTO
<3>[mmc-err] smc 0 err, cmd 5,  RTO
[4.180703] [mmc-err] smc 0 err, cmd 5,  RTO
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.193950] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 
1 timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.211685] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 
1 timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.231790] [mmc-msg] sdc0 set ios: clk 40Hz bm PP pm ON vdd 3.3V width 
1 timing LEGACY(SDR12) dt B
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.247141] [mmc-err] smc 0 err, cmd 2,  RTO
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.255473] [mmc-err] smc 0 err, cmd 2,  RTO
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.263814] [mmc-err] smc 0 err, cmd 2,  RTO
<3>[mmc-err] smc 0 err, cmd 2,  RTO
[4.272123] [mmc-err] smc 0 err, cmd 2,  RTO
<3>mmc0: error -110 whilst initialising SD card
[4.280665] mmc0: error -110 whilst initialising SD card
<6>[mmc-msg] sdc0 set ios: clk 40Hz bm OD pm ON vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.294322] [mmc-msg] sdc0 set ios: clk 40Hz bm OD pm ON vdd 3.3V width 
1 timing LEGACY(SDR12) dt B
<3>[mmc-err] smc 0 err, cmd 1,  RTO
[4.307746] [mmc-err] smc 0 err, cmd 1,  RTO
<6>[mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 timing 
LEGACY(SDR12) dt B
[4.320013] [mmc-msg] sdc0 set ios: clk 0Hz bm OD pm OFF vdd 3.3V width 1 
timing LEGACY(SDR12) dt B
<6>[mmc-msg] sdc0 power off
[4.331589] [mmc-msg] sdc0 power off


I am wondering what the issue is the memory card is not the issue at least not 
on native linux on a non embedded system.



-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] How to use socketcan in android application layer

2013-12-20 Thread DrOctavius1

Peter,

Thanks for your socketcan driver!!! please, would be great to have the CAN 
controller documentation, so everybody can help to improve your work.

There is an Android image for other processor (I.mx6) that has CANBUS 
(using socketcan) and other I/O support, with some small application 
examples:

Android Jellybean 4.2.2 for EDM1-CF-IMX6 *(Now with .apk utilities for 
GPIO/CANbus/Serial)*

http://www.technexion.com/index.php/support/download-center/edm/edm-modules/edm1-cf-imx6

Regards,

Leandro

El miércoles, 18 de diciembre de 2013 08:26:42 UTC-3, Peter Chen escribió:
>
> Sorry for my poor english.I mean I want to write an APP to send/receive 
> CAN message.Since I use socketcan, so I wonder how to write the APP in a 
> proper way.Do I need to write the HAL, JNI and service?Or I can just use 
> the network programming way.
>
> And for the source code, I put it on my github. Anyone interested can 
> visit via:https://github.com/ryangithub/sunxi-can-driver
>
> 在 2013年12月18日星期三UTC+8下午5时27分59秒，Carlo Caione写道：
>>
>> On Wed, Dec 18, 2013 at 10:16 AM, Peter Chen  wrote: 
>> > hey, guys. 
>> > I'v finished sunxi CAN drive in the socketcan mode.And I write a C 
>> program 
>> > proved it works.I can send and receive packet correctlly. 
>>
>> Glad you were able to get the documentation for CAN 
>>
>> > Since I'm not an android app developer, I wonder how can I write a demo 
>> app 
>> > by using the socketcan method.Can anyone give me some 
>> suggestions.Thaks. 
>>
>> I'm not sure I understood what you mean (if you tested the driver 
>> probably you have already written a demo :) 
>> With socketcan you see the CAN bus as a network interface (canX), so 
>> you can use the socket interface. The fact that you are working with 
>> the CAN bus is totally transparent. 
>> (https://www.kernel.org/doc/Documentation/networking/can.txt) 
>>
>> BTW, if willing, please post the source code for review :) 
>>
>> -- 
>> Carlo Caione 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Sun8i (A23) spotted in the wild.

2013-12-20 Thread Luc Verhaegen

On Thu, Dec 19, 2013 at 12:32:24AM +0100, Luc Verhaegen wrote:
> I tried to order myself one of those cheap Q88 tablets with an A13 just 
> now. Big was my surprise when i got it and popped it open, as i was 
> staring at an A23.
> 
> Bad news all round really:
> * fully locked down android, no root, no adb. I will give another root 
> exploit a try tomorrow.
> * our fel utility does not work.
> * we of course have no code for u-boot or linux yet.
> * nothing on the serial port.
> 
> This device is a really serious GPL violator. They even went as far as 
> removing all open source licenses from the About section under android 
> settings.
> 
> What we do know:
> * two obvious serial pads (which are not sending out anything atm)
> * it tries to boot off SD when a likely candidate is there
> * it has a 3.4.39 kernel, and the /proc/config.gz was world readable
> (this is where the string sun8i was found).
> * HW is an A23 which is a bga, with an AXP223 companion
> 
> Board picture is available at the device page: 
> http://linux-sunxi.org/Ippo_q8h
> 
> Luc Verhaegen.

In the meantime, adb access has been figured out and the device has been 
rooted. All is documented on the page.

script.bin has been fetched, and is available from:
http://dl.linux-sunxi.org/users/libv/ippo_q8h/

Luc Verhaegen.

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] [PATCH] Add to W1_SUNX1 depends from W1_MASTER_GPIO

2013-12-20 Thread Gerardo Di Iorio

Signed-off-by: Gerardo Di Iorio 
---
 drivers/w1/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/w1/Kconfig b/drivers/w1/Kconfig
index d61d211..624213a 100644
--- a/drivers/w1/Kconfig
+++ b/drivers/w1/Kconfig
@@ -26,7 +26,7 @@ config W1_CON
  3. Replies to userspace commands.

 config W1_SUNXI
-   depends on GPIO_SUNXI
+   depends on GPIO_SUNXI && W1_MASTER_GPIO
tristate "1-wire sunxi support"
default n
--- help ---
--
1.8.4.2

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] Re: [PATCH v2 2/2] ARM: sun4i/sun7i: RTC driver

2013-12-20 Thread Alessandro Zummo

On Tue, 22 Oct 2013 16:23:13 +0100
Maxime Ripard  wrote:

> > +   platform_set_drvdata(pdev, chip);
> > +   chip->dev = &pdev->dev;

 is chip->dev ever used?

 Acked-by: Alessandro Zummo 

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] zet6221 ts driver testing

2013-12-20 Thread Olliver Schinagl


On 20-12-13 11:34, Oviron Electronics wrote:

Dear Oliver

Thank You for reply.

Now this is a far more civilized mail.

We received sample code from ZET a long time ago and is uploaded to our 
wiki I think and if I'm not mistaken posted on this mailing list, but it 
wasn't something you could just drop in and compile.


Wingrime took this code and wrote a sample driver, 
http://github.com/wingrime that should work under linux.


The latest lichee kernel from Allwinner actually also has a driver in 
their SDK, so should also be useable.


Due to the nature of many touchscreen controllers, it's a hit/miss 
thing, sometimes a driver works, sometimes it needs to be 
tweaked/configured slightly different, it really depends on the 
touchscreen driver IC.


Oliver

I'm experienced in making hardware and PIC ASSEMBLER.
I build my own PCB with 3SC6410 stamp module and I want to use ZET6221
capacitive TSP and AT070TN94 S70 LCD.

My TOTAL LINUX experience is 5 days and 1 day programing in C.So I need
to compile my LINUX kernel.
A friend helped me to install compiler and toolchain. I learned how to
configure and make zImage, how to add new driver. But when compiling
there are some errors. I made corrections and zImage is ready now will
investigate what happens if the driver works ...


If You help me to get it working would be fine. I just wanted to get
working driver and adapt GPIO to my system.


**

Best Regards
*
*
*ILIAN*
*
*

On 20 December 2013 07:16, Olliver Schinagl mailto:oliver+l...@schinagl.nl>> wrote:

On 19-12-13 16:15, oviro...@gmail.com  wrote:

Hello
I need to include ZET6221 driver for 3SC6410 FriendlyArm board.
Can someone send source files ?

I think you confuse linux-sunxi with ZET, so maybe ask them.

As for our RE sources or submitted sources, I'm sure you are able to
use google and find what was posted to this list (which is publicly
archived) and/or check wingrime's git account for his efforts.

Heck even the first few google results for zet6221 yield the proper
results, so do at least SOME homework.

Oliver



--
You received this message because you are subscribed to a topic in
the Google Groups "linux-sunxi" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/__topic/linux-sunxi/_y0NOJL-4YU/__unsubscribe
.
To unsubscribe from this group and all of its topics, send an email
to linux-sunxi+unsubscribe@__googlegroups.com
.
For more options, visit https://groups.google.com/__groups/opt_out
.


--
You received this message because you are subscribed to the Google
Groups "linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] zet6221 ts driver testing

2013-12-20 Thread Oviron Electronics

Dear Oliver

Thank You for reply.
I'm experienced in making hardware and PIC ASSEMBLER.
I build my own PCB with 3SC6410 stamp module and I want to use ZET6221
capacitive TSP and AT070TN94 S70 LCD.

My TOTAL LINUX experience is 5 days and 1 day programing in C.So I need to
compile my LINUX kernel.
A friend helped me to install compiler and toolchain. I learned how to
configure and make zImage, how to add new driver. But when compiling there
are some errors. I made corrections and zImage is ready now will
investigate what happens if the driver works ...

Regards

*Ilian Tsachev*
*General manager*
Oviron  Electronics Ltd.
Bulgaria, Varna
Tel. +359 887 626483
www.ovironelectronics.com

*P* *Please consider the environment before printing this email*

On 20 December 2013 07:16, Olliver Schinagl  wrote:

> On 19-12-13 16:15, oviro...@gmail.com wrote:
>
>> Hello
>> I need to include ZET6221 driver for 3SC6410 FriendlyArm board.
>> Can someone send source files ?
>>
> I think you confuse linux-sunxi with ZET, so maybe ask them.
>
> As for our RE sources or submitted sources, I'm sure you are able to use
> google and find what was posted to this list (which is publicly archived)
> and/or check wingrime's git account for his efforts.
>
> Heck even the first few google results for zet6221 yield the proper
> results, so do at least SOME homework.
>
> Oliver
>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "linux-sunxi" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/linux-sunxi/_y0NOJL-4YU/unsubscribe.
> To unsubscribe from this group and all of its topics, send an email to
> linux-sunxi+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] zet6221 ts driver testing

2013-12-20 Thread Oviron Electronics

Dear Oliver

Thank You for reply.
I'm experienced in making hardware and PIC ASSEMBLER.
I build my own PCB with 3SC6410 stamp module and I want to use ZET6221
capacitive TSP and AT070TN94 S70 LCD.

My TOTAL LINUX experience is 5 days and 1 day programing in C.So I need to
compile my LINUX kernel.
A friend helped me to install compiler and toolchain. I learned how to
configure and make zImage, how to add new driver. But when compiling there
are some errors. I made corrections and zImage is ready now will
investigate what happens if the driver works ...

If You help me to get it working would be fine. I just wanted to get
working driver and adapt GPIO to my system.

Best Regards

*ILIAN*

On 20 December 2013 07:16, Olliver Schinagl  wrote:

> On 19-12-13 16:15, oviro...@gmail.com wrote:
>
>> Hello
>> I need to include ZET6221 driver for 3SC6410 FriendlyArm board.
>> Can someone send source files ?
>>
> I think you confuse linux-sunxi with ZET, so maybe ask them.
>
> As for our RE sources or submitted sources, I'm sure you are able to use
> google and find what was posted to this list (which is publicly archived)
> and/or check wingrime's git account for his efforts.
>
> Heck even the first few google results for zet6221 yield the proper
> results, so do at least SOME homework.
>
> Oliver
>
>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "linux-sunxi" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/linux-sunxi/_y0NOJL-4YU/unsubscribe.
> To unsubscribe from this group and all of its topics, send an email to
> linux-sunxi+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Юрий Пухальский

Oh, sorry. Silly me, i had dd'ed the uboot to wrong device =*)
Kernel started ok.
No VGA output, but probably it's as intended.


On Fri, Dec 20, 2013 at 1:04 PM, Юрий Пухальский  wrote:

> I've configured it as a13-olinuxino_config. Is it ok?
>
>
> On Fri, Dec 20, 2013 at 12:57 PM, Юрий Пухальский wrote:
>
>> Hi!
>>
>> Yes, that's A13.
>> I believe I've installed your uboot:
>>
>> [remote "origin"]
>> url = https://github.com/jwrdegoede/u-boot-sunxi.git
>> fetch = +refs/heads/*:refs/remotes/origin/*
>> [branch "sunxi-next"]
>> remote = origin
>> merge = refs/heads/sunxi-next
>>
>> Is there any way to make sure from the uboot prompt?
>>
>>
>> On Fri, Dec 20, 2013 at 11:29 AM, Hans de Goede wrote:
>>
>>> Hi,
>>>
>>>
>>> On 12/19/2013 10:49 PM, Юрий Пухальский wrote:
>>>
 Good UTC night!


 Got somewhat further, yet still there are problems.
 Is there anything i should change in kernel cmdline maybe?

>>>
>>> Is this a sun5i device, iow A10s or A13 SOC based ? If so you
>>> need to build and boot with my sunxi-next u-boot branch:
>>>
>>> https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next
>>>
>>> The only time I've seen those clock update timeout errors is
>>> on sun5i with an unfixed uboot.
>>>
>>>
>>> Regards,
>>>
>>> Hans
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "linux-sunxi" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>> topic/linux-sunxi/prLRvZAHFvc/unsubscribe.
>>> To unsubscribe from this group and all of its topics, send an email to
>>> linux-sunxi+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> --
>> Point of presence: http://aikipooh.ipernity.com
>>
>
>
>
> --
> Point of presence: http://aikipooh.ipernity.com
>



-- 
Point of presence: http://aikipooh.ipernity.com

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Юрий Пухальский

I've configured it as a13-olinuxino_config. Is it ok?


On Fri, Dec 20, 2013 at 12:57 PM, Юрий Пухальский wrote:

> Hi!
>
> Yes, that's A13.
> I believe I've installed your uboot:
>
> [remote "origin"]
> url = https://github.com/jwrdegoede/u-boot-sunxi.git
> fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "sunxi-next"]
> remote = origin
> merge = refs/heads/sunxi-next
>
> Is there any way to make sure from the uboot prompt?
>
>
> On Fri, Dec 20, 2013 at 11:29 AM, Hans de Goede wrote:
>
>> Hi,
>>
>>
>> On 12/19/2013 10:49 PM, Юрий Пухальский wrote:
>>
>>> Good UTC night!
>>>
>>>
>>> Got somewhat further, yet still there are problems.
>>> Is there anything i should change in kernel cmdline maybe?
>>>
>>
>> Is this a sun5i device, iow A10s or A13 SOC based ? If so you
>> need to build and boot with my sunxi-next u-boot branch:
>>
>> https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next
>>
>> The only time I've seen those clock update timeout errors is
>> on sun5i with an unfixed uboot.
>>
>>
>> Regards,
>>
>> Hans
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "linux-sunxi" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/
>> topic/linux-sunxi/prLRvZAHFvc/unsubscribe.
>> To unsubscribe from this group and all of its topics, send an email to
>> linux-sunxi+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Point of presence: http://aikipooh.ipernity.com
>



-- 
Point of presence: http://aikipooh.ipernity.com

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Юрий Пухальский

Hi!

Yes, that's A13.
I believe I've installed your uboot:

[remote "origin"]
url = https://github.com/jwrdegoede/u-boot-sunxi.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "sunxi-next"]
remote = origin
merge = refs/heads/sunxi-next

Is there any way to make sure from the uboot prompt?


On Fri, Dec 20, 2013 at 11:29 AM, Hans de Goede  wrote:

> Hi,
>
>
> On 12/19/2013 10:49 PM, Юрий Пухальский wrote:
>
>> Good UTC night!
>>
>>
>> Got somewhat further, yet still there are problems.
>> Is there anything i should change in kernel cmdline maybe?
>>
>
> Is this a sun5i device, iow A10s or A13 SOC based ? If so you
> need to build and boot with my sunxi-next u-boot branch:
>
> https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next
>
> The only time I've seen those clock update timeout errors is
> on sun5i with an unfixed uboot.
>
>
> Regards,
>
> Hans
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "linux-sunxi" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/linux-sunxi/prLRvZAHFvc/unsubscribe.
> To unsubscribe from this group and all of its topics, send an email to
> linux-sunxi+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Point of presence: http://aikipooh.ipernity.com

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

2013-12-20 Thread Maxime Ripard

Hi Hans,

On Fri, Dec 20, 2013 at 08:29:46AM +0100, Hans de Goede wrote:
> Hi,
> 
> On 12/19/2013 10:49 PM, Юрий Пухальский wrote:
> >Good UTC night!
> >
> >
> >Got somewhat further, yet still there are problems.
> >Is there anything i should change in kernel cmdline maybe?
> 
> Is this a sun5i device, iow A10s or A13 SOC based ? If so you
> need to build and boot with my sunxi-next u-boot branch:
> 
> https://github.com/jwrdegoede/u-boot-sunxi/commits/sunxi-next
> 
> The only time I've seen those clock update timeout errors is
> on sun5i with an unfixed uboot.

It would be really great if it was to work without any changes in
u-boot. You shouldn't really make assumption on which bootloader
you're using, which configuration you've chosen for it, or which
version you're using.

The kernel should be able to setup everything needed on its own (but
the RAM, of course).

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com


signature.asc
Description: Digital signature

Re: [linux-sunxi] zet6221 ts driver testing

2013-12-20 Thread Olliver Schinagl


On 19-12-13 16:15, oviro...@gmail.com wrote:

Hello
I need to include ZET6221 driver for 3SC6410 FriendlyArm board.
Can someone send source files ?

I think you confuse linux-sunxi with ZET, so maybe ask them.

As for our RE sources or submitted sources, I'm sure you are able to use 
google and find what was posted to this list (which is publicly 
archived) and/or check wingrime's git account for his efforts.


Heck even the first few google results for zet6221 yield the proper 
results, so do at least SOME homework.


Oliver




--
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[linux-sunxi] Waiting for root device /dev/mmcblk0p2...

Re: [linux-sunxi] mmc errors

Re: [linux-sunxi] Sun8i (A23) spotted in the wild.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

[linux-sunxi] Re: [PATCH v4 2/2] ARM: sun4i/sun7i: RTC driver

[linux-sunxi] [PATCH 0/3] ARM: sunxi: Add A31 High Speed Timer Support

[linux-sunxi] [PATCH 3/3] ARM: sun6i: a31: Add support for the High Speed Timers

[linux-sunxi] [PATCH 2/3] clocksource: sun5i: Add support for reset controller

[linux-sunxi] [PATCH 1/3] reset: Add of_reset_control_get

Re: [linux-sunxi] mmc errors

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

Re: [linux-sunxi] Sun8i (A23) spotted in the wild.

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

[linux-sunxi] mmc errors

Re: [linux-sunxi] How to use socketcan in android application layer

Re: [linux-sunxi] Sun8i (A23) spotted in the wild.

[linux-sunxi] [PATCH] Add to W1_SUNX1 depends from W1_MASTER_GPIO

[linux-sunxi] Re: [PATCH v2 2/2] ARM: sun4i/sun7i: RTC driver

Re: [linux-sunxi] zet6221 ts driver testing

Re: [linux-sunxi] zet6221 ts driver testing

Re: [linux-sunxi] zet6221 ts driver testing

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

Re: [linux-sunxi] Re: Upstreaming sunxi mmc support

Re: [linux-sunxi] zet6221 ts driver testing

26 matches

Site Navigation

Mail list logo

Footer information