Re: [U-Boot-Users] UBOOT port to i.MX27ADS - NAND issues
On Fri, Oct 31, 2008 at 07:35:42PM +0530, Tiju wrote: Great! Care to send patches? That would help answering further questions as well.. Sorry, I know its a basic question but how do I make a patch file? Else I can send you the file I modified. It's basically diff -u old-file.c new-file.c Bug you should probably read this: http://lxr.linux.no/linux/Documentation/SubmittingPatches rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] RFC: mailing list transfer
On Fri, Aug 01, 2008 at 05:17:49PM +0200, Wolfgang Denk wrote: Do you think this is a reasonable plan? Any hints, ideas, tips? Yes, good idea! Local infrastructure has turned out to be much more reliable than services like SF these days. rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
[U-Boot-Users] [PATCH U-Boot-v2] at91sam9260ek: add defconfig
The board has no defconfig file; add one. Signed-off-by: Robert Schwebel [EMAIL PROTECTED] --- arch/arm/configs/at91sam9260ek_defconfig | 189 +++ 1 file changed, 189 insertions(+) Index: u-boot-v2/arch/arm/configs/at91sam9260ek_defconfig === --- /dev/null +++ u-boot-v2/arch/arm/configs/at91sam9260ek_defconfig @@ -0,0 +1,189 @@ +# +# Automatically generated make config: don't edit +# U-Boot version: 2.0.0-rc5-git +# Tue Jul 29 17:35:38 2008 +# +CONFIG_ARCH_TEXT_BASE=0x23f0 +CONFIG_BOARDINFO=Atmel 91SAM9260-EK +# CONFIG_BOARD_LINKER_SCRIPT is not set +CONFIG_GENERIC_LINKER_SCRIPT=y +CONFIG_ARM=y +CONFIG_ARM926EJS=y +CONFIG_ARCH_AT91SAM9=y +CONFIG_ARCH_AT91SAM9260=y +# CONFIG_MACH_MX1ADS is not set +# CONFIG_MACH_SCB9328 is not set +# CONFIG_MACH_PCM038 is not set +# CONFIG_MACH_IMX27ADS is not set +# CONFIG_MACH_ECO920 is not set +# CONFIG_MACH_NXDB500 is not set +# CONFIG_MACH_PCM037 is not set +# CONFIG_MACH_OMAP is not set +CONFIG_MACH_AT91SAM9260_EK=y + +# +# Arm specific settings +# +CONFIG_CMDLINE_TAG=y +CONFIG_SETUP_MEMORY_TAGS=y +# CONFIG_INITRD_TAG is not set +CONFIG_GREGORIAN_CALENDER=y +CONFIG_HAS_KALLSYMS=y +CONFIG_HAS_MODULES=y +CONFIG_CMD_MEMORY=y +CONFIG_ENV_HANDLING=y + +# +# General Settings +# + +# +# memory layout +# +CONFIG_HAVE_CONFIGURABLE_TEXT_BASE=y +CONFIG_TEXT_BASE=0xa7f0 +CONFIG_HAVE_CONFIGURABLE_MEMORY_LAYOUT=y +CONFIG_MEMORY_LAYOUT_DEFAULT=y +# CONFIG_MEMORY_LAYOUT_FIXED is not set +CONFIG_STACK_SIZE=0x8000 +CONFIG_MALLOC_SIZE=0x40 +# CONFIG_BROKEN is not set +# CONFIG_EXPERIMENTAL is not set +CONFIG_PROMPT=uboot: +CONFIG_BAUDRATE=115200 +CONFIG_CMDLINE_EDITING=y +CONFIG_AUTO_COMPLETE=y +CONFIG_LONGHELP=y +CONFIG_CBSIZE=1024 +CONFIG_MAXARGS=16 +CONFIG_SHELL_HUSH=y +# CONFIG_SHELL_SIMPLE is not set +CONFIG_GLOB=y +CONFIG_PROMPT_HUSH_PS2= +CONFIG_DYNAMIC_CRC_TABLE=y +CONFIG_ERRNO_MESSAGES=y +CONFIG_TIMESTAMP=y +CONFIG_CONSOLE_ACTIVATE_FIRST=y +# CONFIG_OF_FLAT_TREE is not set +CONFIG_PARTITION=y +CONFIG_DEFAULT_ENVIRONMENT=y +CONFIG_DEFAULT_ENVIRONMENT_PATH=board/at91sam9260ek/env + +# +# Debugging +# +# CONFIG_DEBUG_INFO is not set +# CONFIG_ENABLE_FLASH_NOISE is not set +# CONFIG_ENABLE_PARTITION_NOISE is not set +# CONFIG_ENABLE_DEVICE_NOISE is not set + +# +# Commands +# + +# +# scripting +# +CONFIG_CMD_EDIT=y +CONFIG_CMD_SLEEP=y +CONFIG_CMD_SAVEENV=y +CONFIG_CMD_LOADENV=y +CONFIG_CMD_EXPORT=y +CONFIG_CMD_PRINTENV=y +CONFIG_CMD_HELP=y +CONFIG_CMD_READLINE=y + +# +# file commands +# +CONFIG_CMD_LS=y +CONFIG_CMD_RM=y +CONFIG_CMD_CAT=y +CONFIG_CMD_MKDIR=y +CONFIG_CMD_RMDIR=y +CONFIG_CMD_CP=y +CONFIG_CMD_PWD=y +CONFIG_CMD_CD=y +CONFIG_CMD_MOUNT=y +CONFIG_CMD_UMOUNT=y + +# +# console +# +CONFIG_CMD_CLEAR=y +CONFIG_CMD_ECHO=y + +# +# memory +# +# CONFIG_CMD_LOADB is not set +CONFIG_CMD_MEMINFO=y +CONFIG_CMD_CRC=y +CONFIG_CMD_MTEST=y +# CONFIG_CMD_MTEST_ALTERNATIVE is not set + +# +# flash +# +CONFIG_CMD_FLASH=y +# CONFIG_CMD_NAND is not set + +# +# booting +# +CONFIG_CMD_BOOTM=y +# CONFIG_CMD_BOOTM_ZLIB is not set +# CONFIG_CMD_BOOTM_BZLIB is not set +# CONFIG_CMD_BOOTM_SHOW_TYPE is not set +CONFIG_CMD_RESET=y +CONFIG_CMD_GO=y +CONFIG_CMD_TIMEOUT=y +CONFIG_CMD_PARTITION=y +CONFIG_CMD_TEST=y +CONFIG_NET=y +CONFIG_NET_BOOTP=y +CONFIG_NET_DHCP=y +# CONFIG_NET_RARP is not set +# CONFIG_NET_SNTP is not set +# CONFIG_NET_NFS is not set +CONFIG_NET_PING=y +CONFIG_NET_TFTP=y + +# +# Drivers +# + +# +# serial drivers +# +# CONFIG_DRIVER_SERIAL_NS16550 is not set +CONFIG_DRIVER_SERIAL_ATMEL=y +CONFIG_MIIPHY=y + +# +# Network drivers +# +# CONFIG_DRIVER_NET_SMC911X is not set +CONFIG_DRIVER_NET_MACB=y + +# +# SPI drivers +# +# CONFIG_SPI is not set + +# +# flash drivers +# +CONFIG_DRIVER_CFI=y +# CONFIG_DRIVER_CFI_NEW is not set +CONFIG_DRIVER_CFI_OLD=y +CONFIG_CFI_BUFFER_WRITE=y +# CONFIG_NAND is not set + +# +# Filesystem support +# +# CONFIG_FS_CRAMFS is not set +CONFIG_FS_RAMFS=y +CONFIG_FS_DEVFS=y +CONFIG_CRC32=y -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url
Re: [U-Boot-Users] i.MX27ADS patch/port for UBOOT
On Mon, Jul 28, 2008 at 10:43:39PM +0530, Tiju wrote: I have a freescale based MX27ADS development board. I am trying to port u-boot to this board. Is there a port thats already available? If not kindly suggest what could be the nearest port to this board? There is an (incomplete) u-boot-v2 port for the ADS. Improvements are welcome. rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
[U-Boot-Users] [PATCH U-Boot-v2] at91sam9260ek: fix names
Fix some left-overs from copy and paste.
Signed-off-by: Robert Schwebel [EMAIL PROTECTED]
---
board/at91sam9260ek/init.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
Index: u-boot-v2/board/at91sam9260ek/init.c
===
--- u-boot-v2.orig/board/at91sam9260ek/init.c
+++ u-boot-v2/board/at91sam9260ek/init.c
@@ -1,5 +1,5 @@
/*
- * Copyright (C) 2007 Sascha Hauer, Pengutronix
+ * Copyright (C) 2007 Sascha Hauer, Pengutronix
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License as
@@ -98,7 +98,7 @@ static struct device_d macb_dev = {
.type = DEVICE_TYPE_ETHER,
};
-static int pcm038_devices_init(void)
+static int at91sam9260ek_devices_init(void)
{
register_device(sdram_dev);
register_device(nand_dev);
@@ -110,9 +110,9 @@ static int pcm038_devices_init(void)
return 0;
}
-device_initcall(pcm038_devices_init);
+device_initcall(at91sam9260ek_devices_init);
-static struct device_d pcm038_serial_device = {
+static struct device_d at91sam9260ek_serial_device = {
.name = atmel_serial,
.id = cs0,
.map_base = USART3_BASE,
@@ -120,10 +120,10 @@ static struct device_d pcm038_serial_dev
.type = DEVICE_TYPE_CONSOLE,
};
-static int pcm038_console_init(void)
+static int at91sam9260ek_console_init(void)
{
- register_device(pcm038_serial_device);
+ register_device(at91sam9260ek_serial_device);
return 0;
}
-console_initcall(pcm038_console_init);
+console_initcall(at91sam9260ek_console_init);
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [PATCH U-Boot-v2] at91sam9260ek: fix names
On Tue, Jul 29, 2008 at 05:53:37PM +0200, Robert Schwebel wrote: Fix some left-overs from copy and paste. However, the board still fails to build, looks like you've forgotten to change in some of the Pengutronix TechWeek stuff: [EMAIL PROTECTED]:u-boot-v2$ make ARCH=arm CROSS_COMPILE=/opt/OSELAS.Toolchain-1.1.1/arm-v4t-linux-gnueabi/gcc-4.1.2-glibc-2.5-kernel-2.6.18/bin/arm-v4t-linux-gnueabi- CHK include/linux/version.h CHK include/linux/utsrelease.h CC drivers/net/macb.o In file included from drivers/net/macb.c:48: include/asm/arch/clk.h: In function 'get_macb_pclk_rate': include/asm/arch/clk.h:31: error: 'AT91_MASTER_CLOCK' undeclared (first use in this function) include/asm/arch/clk.h:31: error: (Each undeclared identifier is reported only once include/asm/arch/clk.h:31: error: for each function it appears in.) include/asm/arch/clk.h: In function 'get_usart_clk_rate': include/asm/arch/clk.h:36: error: 'AT91_MASTER_CLOCK' undeclared (first use in this function) make[2]: *** [drivers/net/macb.o] Error 1 make[1]: *** [drivers/net] Error 2 make: *** [drivers] Error 2 [EMAIL PROTECTED]:u-boot-v2$ rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] i.MX27ADS patch/port for UBOOT
On Tue, Jul 29, 2008 at 10:25:41PM +0530, Tiju wrote: How do I get the MX27ADS u-bootv2 patches? It is in the u-boot-v2 git tree: http://git.denx.de/?p=u-boot/u-boot-v2.git;a=summary rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] Changing u-boot relocation scheme
On Wed, Jul 23, 2008 at 10:39:00AM -0700, vb wrote: While this relocation is seamless for u-boot in its released form, it becomes a pain each time a module needs to be added (not necessarily for following release to the Open Source community, for instance used for inhouse installations which include tens of thousand units for some companies). If these added modules were not written in position independent manner (namely, using structures with multiple stage indirect pointers interleaved with data), the effort to make these modules work in u-boot is very exhausting. Note that in U-Boot-v2 we have loadable module support; code can EXPORT_SYMBOL() public APIs to other components, which, for example, can be such custom modules. The mechanism was invented for the scenario you describe above. It comes for a cost (footprint), but the overhead is not so big as one might think. You can play around with the feature by building the sandbox target, which is a user-mode-u-boot (port of u-boot to Linux userspace). rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] V2 status, (Was Re: V2: Error in recent check-in)
On Tue, Jul 08, 2008 at 12:36:13AM -0700, Chris Zankel wrote: I really like the structure of V2 but my fear is that there's not enough man power behind it. It depends on how far people's interest will go in the future. It turned out to be relatively easy to port things over to a solid design once a feature is really needed by somebody. We are using Phytec's i.MX27 board, so we are 'stuck' with that version. Consider it a feature, you can help lowering the (ifdef) entropy in the universe :-) Which functionality are you missing? I'm sorry if this questions has been asked before, but do you see more momentum to push for V2? It depends on community and customer interest. It's probably too early to ask for a separate V2 mailing list? Yes; at the moment it's probably better to leave the traffic here. It still can be split up once it goes up significantly. rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [PATCH v2] Update Freescale sys_eeprom.c to handle CCID formats
On Sun, Jun 22, 2008 at 05:03:55PM -0500, Timur Tabi wrote: Sounds complicated and interesting. I might think about it some more later. Hmm, I don't think that it's really complicated. It's only that it needs yet another arbitrary definition of what certain strings mean - which was a cause for tree breakage over and over again in the past. But as oftree seems to be designed around arbitrary strings, I suppose it's just a matter of agreeing on the same nomenclature. rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [PATCH v2] Update Freescale sys_eeprom.c to handle CCID formats
Hi, On Fri, Jun 20, 2008 at 09:59:03AM -0500, Timur Tabi wrote: Update the sys_eeprom.c file to handle both NXID and CCID EEPROM formats. The NXID format replaces the older CCID format, but it's important to support both since most boards out there still use the CCID format. This change is in preparation for using one file to handle both formats. This will also unify EEPROM support for all Freescale 85xx and 86xx boards. Also update the 86xx board header files to use the standard CFG_I2C_EEPROM_ADDR instead of ID_EEPROM_ADDR. I don't know what NXID and CCID is, but have you seen Wolfram's proposal for sub-devicetrees? http://ozlabs.org/pipermail/linuxppc-dev/2008-June/058263.html Our aim here is to put device tree sniplets into eeproms or flash areas; we have several boards here that consist of - a module - a base board - maybe an extension board and having sub devicetrees would make it possible to simply put the devicetree for each component into a piece of storage *on the component*. So the bootloader and later Linux would be able to build the whole tree from these sniplets. Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [Patch 0/9] U-boot-V2: Introduce I2C support for SDP3430
On Wed, Jun 18, 2008 at 11:04:21AM -0500, Menon, Nishanth wrote: Hmm... flexibility Vs size.. the age old argument ;). Well, the code we have in u2 today has shown that you can get both, if done carefully :) When I started considering i2c I pulled code from U-Boot v1 and started putting in u-boot v2, then realized I was barking up the wrong tree. I then realized that probably it is better to pull in the linux i2c arch in to u-boot v2 and add flags to enable/disable features to control the size. Having a Kconfig does help a ton. The new style drivers were perfect to fit into u-boot-v2 architecture + I get to enable folks who already have linux drivers to pull it down to u-boot v2 with very little effort. The learning curve is smaller, infact, almost non-existant. Right; nevertheless, don't forget that this is a bootloader, and our aim is to have a codebase which is as clear as possible right from the beginning. I think the best choice is selective addition as the need arises. We may not need V4L2 and similar things.. Where we can make compatibility happen, that would be good IMHO. We can then proceed with customizing and improving it to our needs. Why reinvent the wheel? We might need a wheel with slightly different requirements :-) So I suppose the right way to proceed is: - let's first define use cases for what you want to achieve with the i2c support in u-boot-v2 - let's have a look at how it would integrate into the device/driver model and how the user-visible API would look like - write a small framework for i2c, with host+algo+device parts, heavily inspired by the best of Linux and the best of u-boot/u-boot-v2. That worked out very well for the features we currently have in u2. Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [Patch 0/9] U-boot-V2: Introduce I2C support for SDP3430
On Wed, Jun 18, 2008 at 10:39:30AM -0500, Timur Tabi wrote: It does not have i2c support. And IMHO, using kernel like i2c addition in U-Boot v2 is appropriate. Why this is not a bloat U-Boot v2? If it isn't, then it means that U-Boot V2 will be pretty bloated in general. Please have a look at the code base first and post *then* instead of speculating. Sounds to me like U-Boot V2 is just a repacked Linux kernel. We could probably save ourselves a lot of trouble if we just took the DDR and CPU register initialization code in U-Boot and moved it to the kernel. It might be a good opportunity to check the code now ... :-) rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [Patch 1/9] U-boot-V2:ID: Sync mod_devicetable
On Wed, Jun 18, 2008 at 07:33:50AM -0500, Menon, Nishanth wrote:
include/linux/mod_devicetable.h | 382
This is u-boot, not linux. Please let's not introduce more of the
copy-and-paste things we have around from the past.
+/*
+ * Device tables which are exported to userspace via
+ * scripts/mod/file2alias.c. You must keep that file in sync with this
+ * header.
+ */
U-Boot doesn't have userspace.
+
+#ifndef LINUX_MOD_DEVICETABLE_H
+#define LINUX_MOD_DEVICETABLE_H
+
+#ifdef __KERNEL__
+#include linux/types.h
+typedef unsigned long kernel_ulong_t;
+#endif
No Linux, no __KERNEL__.
+#define PCI_ANY_ID (~0)
Until now, there is no PCI support in u-boot-v2. It would be great to
have it, but please let's first add PCI support and then stuff that
depends on it :-)
+struct pci_device_id {
+ __u32 vendor, device; /* Vendor and device ID or
PCI_ANY_ID*/
+ __u32 subvendor, subdevice; /* Subsystem ID's or PCI_ANY_ID */
+ __u32 class, class_mask;/* (class,subclass,prog-if) triplet */
+ kernel_ulong_t driver_data; /* Data private to the driver */
+};
I assume you don't have your controller attached via pci; so before we
have proper PCI support, please don't do this. It might happen that it
turns out that the data model above doesn't fit u-boot's needs in the
end.
Pushing in stuff just because it was there let's people assume that
someone has *thought* about PCI in u-boot-v2. The net one comes and
tries to use it and *bang*. And even worse, if somebody tries to really
add PCI support, he will probably collide with this.
+#define IEEE1394_MATCH_VENDOR_ID 0x0001
+#define IEEE1394_MATCH_MODEL_ID0x0002
+#define IEEE1394_MATCH_SPECIFIER_ID0x0004
+#define IEEE1394_MATCH_VERSION 0x0008
We also don't have 1394.
+ * Device table entry for new style table-driven USB drivers.
+ * User mode code can read these tables to choose which modules to load.
+ * Declare the table as a MODULE_DEVICE_TABLE.
Nevertheless, this new style model is a good idea and is worth being
considered for the concept of i2c in u-boot-v2.
+/**
+ * struct usb_device_id - identifies USB devices for probing and hotplugging
+ * @match_flags: Bit mask controlling of the other fields are used to match
If you add header documentation, please use Doygen-style comments.
U-Boot-v2 has a Doygen-generated manual which was layed out carefully,
so please
a) check what the real interfaces of a subsystem are
b) document them
c) integrate them into the main manual, in a way that it is readable and
can be used as an introduction for somebody who wants to start
learning about the concepts.
+/* Some useful macros to use to create struct usb_device_id */
Argh, we don't have USB in u-boot-v2 yet. Same arguments as above with
PCI.
+/* s390 CCW devices */
Although u-boot-v2 on S390 would surely be a cool idea, I assume that
doesn't fit here.
+struct acpi_device_id {
+ __u8 id[ACPI_ID_LEN];
+ kernel_ulong_t driver_data;
+};
... and there is also no ACPI support available yet.
+struct pnp_device_id {
+ __u8 id[PNP_ID_LEN];
+ kernel_ulong_t driver_data;
+};
... and no pnp.
+struct of_device_id {
+ charname[32];
+ chartype[32];
+ charcompatible[128];
+#ifdef __KERNEL__
+ void*data;
+#else
+ kernel_ulong_t data;
+#endif
+};
No of-tree support here. U-Boot has to *provide* an oftree, not to
consume one.
I leave the other subsystems out that are not available yet.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
U-Boot-Users mailing list
U-Boot-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [Patch 0/9] U-boot-V2: Introduce I2C support for SDP3430
Hi, On Wed, Jun 18, 2008 at 01:48:26PM -0500, Menon, Nishanth wrote: What issues do you see with the proposed patch set I have send out - other than it bases itself on Linux kernel? I've commented your first patch in the series; in short: - It shows nicely that it is easy to copy things over from Linux - that's a good sign that we didn't do too many things the wrong way. But note, it is *not* the main intention of u-boot-v2 to be a Linux clone. It is a bootloader, and it tries to be one with a neat design, combining the best of POSIX, Linux and U-Boot-v1. Copying *ideas* is good, but let's do it in a way that it still is u-boot. - Please don't bring in things which are not part of the current code base. If you add code for subsystems, the subsystems must be there first and *then* their users. Otherwhise we bloat the codebase and we disable the possibility to add *real* support for PCI, USB and S390 later :-) It meets the following requirements: a) does meet all the use cases folks need with i2c: i) bare bone i2c arch - don't use client drivers, just stick around with adapter and use i2c_transfer or smbus ops which ever you'd like. ii) someone wants to write a client for a commonly used device -eeprom or the like.. feel free to do so. No problem with that. iii) does it support multiple buses? Oh yeah it does. So does it support multiples speed busses too. That's also a requirement. b) does it fit in device-driver model? Yep it does. Sure. c) Is it small? I don't see 6K a big overhead considering similar addition due to devfs or nand support.. in fact my adapter driver could be eating a chunk of that 6K. See above. Check how Sascha's code for console, serial or clocksource looks like. It really *looks* like Linux from the outside, but it is much, much smaller and better aligned for bootloader use. Back to my proposal: So I suppose the right way to proceed is: - let's first define use cases for what you want to achieve with the i2c support in u-boot-v2 - let's have a look at how it would integrate into the device/driver model and how the user-visible API would look like - write a small framework for i2c, with host+algo+device parts, heavily inspired by the best of Linux and the best of u-boot/u-boot-v2. Which part of i2c do we actually *need* in the bootloader? What's *your* use case? I assume we need i2c host controllers, that's quite clear. We also need an abstraction for i2c devices. The only devices I have seen which really needed a bootloader driver are a) eeproms b) RTCs c) analog/digital in/outputs (i.e. gpio expanders) Other use cases? Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] [Patch 0/9] U-boot-V2: Introduce I2C support for SDP3430
On Wed, Jun 18, 2008 at 03:21:02PM -0500, Menon, Nishanth wrote: - Please don't bring in things which are not part of the current code base. If you add code for subsystems, the subsystems must be there first and *then* their users. Otherwhise we bloat the codebase and we disable the possibility to add *real* support for PCI, USB and S390 later :-) Acked. Yep will redo that :). Yea, looking forward especially for PCI patches :-) Which part of i2c do we actually *need* in the bootloader? What's *your* use case? I need i2c_transfer -yes - I can customize the changes just for that. I do like i2c_transfers, adapters, clients etc.. my immediate need is rather simple - i2c_transfers. Ok, so let's start with that. I assume we need i2c host controllers, that's quite clear. We also need an abstraction for i2c devices. The only devices I have seen which really needed a bootloader driver are a) eeproms b) RTCs c) analog/digital in/outputs (i.e. gpio expanders) Other use cases? USB Transceivers, power management devices. Yes, but I think what we most of all need is the i2c communication with the device. We should think about if the abstraction of the devices *behind* the bus brings us anything; note that you can do lots of things in scripts in u-boot-v2. Linke writing a shell function for your usb transceivers which just encapsulates the right predefined i2c_read/write operations. Are we ok with i2ctools movement here? Hmm? How do you mean that? rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] MX31ADS: I2C1 bus
On Fri, Jun 06, 2008 at 10:46:16AM +0200, llandre wrote: I downloaded current u-boot repo to perform a simple test on MX31ADS: I just have to verify that an I2C component connected to JP13 is detected by U-Boot (iprobe). So I enabled the I2C support in MX31ADS config file: /* I2C */ #define CONFIG_HARD_I2C 1 #define CONFIG_I2C_MXC1 #define CFG_I2C_MX31_PORT11 #define CFG_I2C_SPEED 10 #define CFG_I2C_SLAVE 0xfe U-Boot builds and boots fine however, when issuing iprobe command, SDA and SCL lines are stuck at ~2.1V. JP6 and JP7 are both in 2-3 position. Am I missing something? That looks like u-boot-v1. Sascha maintains the u-boot-v2 tree, which hopefully doesn't have any such #define cruft any more :-) The v1 port was done by Guennadi Liakhovetski. rsc -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] Booting U-boot from NAND on MX31
On Fri, Jun 06, 2008 at 12:06:18PM -0700, Fabio Estevam wrote: We can succesfully boot U-boot from NOR on a MX31ADS. Has anyone managed to boot U-boot from NAND in any MX31 board? We have recently started working on NAND support for several chips (including the MX31) in u-boot-v2. However, it's not yet production quality. As always: roadmap depends on customer demands ... Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] u-boot v2
On Wed, May 28, 2008 at 03:41:58PM +0200, Kenneth Johansson wrote: I'm just wondering what the status and plans are with the V2 branch. Is the plan that at some future date everyone just stops works on the main branch and switch over to V2 or is the features of V2 going to be ported over one by one. v2 is currently a technology study, lead by Pengutronix developers (mainly Sascha Hauer), which shows where *we* do currently see weak points in the U-Boot design and how things could look in the future. I doubt that there will some point in time where everyone will just switch over; what will happen depends very much on how much people look at the code, see the shiny beauty of these ideas and start contributing :-) People have contributed in the past, they still do, we do active development on it for real life customer projects, because it solves real problems. So it will evolve over the time. Anything else is a matter of community activity. Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] U-Boot V2 question
On Fri, May 02, 2008 at 07:09:44PM -0500, Nishanth Menon wrote: This is with regards to U-Boot V2 .dox files. Are these hand coded or was some WYSIWYG editor generated? E.g.: http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-v2.git;a=blob;f=Documentation/developers_manual.dox;hb=HEAD No, the dox files are hand coded. So you can send patches against them :) Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] Problems with 1.3.3-rc1 on i.MX31ADS
On Sun, Apr 27, 2008 at 12:06:04AM +0300, Felix Radensky wrote: Thanks for adding i.mx31 support to u-boot. Hopefully i.mx27 support will follow soon. i.MX27 is supported in u-boot-v2. Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Re: [U-Boot-Users] iMX27 support status
On Fri, Apr 18, 2008 at 01:32:33PM +0800, yanjun.luo wrote: I'll debug my iMX27 board next month, I know that iMX27ADS use redboot, but I want to use U-BOOT. I checked current code from git, but only find iMX31's code. How about the status of iMX27 support? i.MX27 and the ADS is supported in the u-boot-v2 tree: http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-v2.git;a=summary Note that nobody invested much work in the ADS yet, our forcus was on the phyCORE-i.MX27 board. And when you want to start with Linux, please have a look at our patch series for the board: http://www.pengutronix.de/software/linux-i.MX/index_en.html Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Handelsregister: Amtsgericht Hildesheim, HRA 2686 Hannoversche Str. 2, 31134 Hildesheim, Germany Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9 - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone ___ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
