mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Antony Pavlov <antonynpavlov@gmail.com>
To: Lucas Stach <dev@lynxeye.de>
Cc: barebox@lists.infradead.org
Subject: Tegra2 USB issue
Date: Thu, 24 Jul 2014 20:05:45 +0400	[thread overview]
Message-ID: <20140724200545.009a9c6c143abf1b344721a5@gmail.com> (raw)

Hi!

I have just tested this commit

commit d8bdd537220dd83912949f19ba67029bd1f11c58
Author: Lucas Stach <dev@lynxeye.de>
Date:   Fri Apr 12 12:28:14 2013 +0200

    tegra: switch to proper CPU type
    
    Tegras main CPUs are all ARMv7.
    
    Signed-off-by: Lucas Stach <dev@lynxeye.de>
    Tested-by: Antony Pavlov <antonynpavlov@gmail.com>
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index bb9b47b..dfb7e24 100644
--- a/arch/arm/Kconfig
+++ b/arch/arm/Kconfig
@@ -137,7 +137,7 @@ config ARCH_VEXPRESS
 
 config ARCH_TEGRA
        bool "Nvidia Tegra-based boards"
-       select CPU_ARM926T
+       select CPU_V7
        select HAS_DEBUG_LL
 
 config ARCH_ZYNQ

This commit breaks 'usb' command --- it does not scan devices anymore, just hangs.

I have used codesourcery arm-2013.11 toolchain.

I'll try to check latest barebox from next, but just now I have no means to burn
barebox-tegra20-toshiba-ac100.img into AC100's ROM.

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2014-07-24 15:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 16:05 Antony Pavlov [this message]
2014-07-24 16:08 ` Lucas Stach
2014-07-24 16:46   ` Antony Pavlov
2014-07-24 16:39     ` Lucas Stach
2014-07-24 19:15       ` Antony Pavlov
2014-07-25 16:41   ` Antony Pavlov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140724200545.009a9c6c143abf1b344721a5@gmail.com \
    --to=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=dev@lynxeye.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox