[JOB] Senior Embedded Linux Video Engineer
Wolfgang Denk wrote: Please don't try to reinvent Usenet netiquette, poorly. Begging your pardon, sire. Thanks for the adverb too btw, quite a bonus - amusing, albeit poorly. And speaking of which... Commercial ads, job ofers and the like have always been banned. It's just lately that nobody remembers the good old days any more and everybody thinks he can force his ideas over everybody else. ?! Whoah, if that's the nature of the discussion, fine - count me out. Oh, and FYI - the good old days also involved rock musicians in spandex, and ... well ... whatever. If you were referring to me, then I retract any such force without hesitation - because until you told me otherwise, I was entirely ignorant to its existence. To be honest, I'm still not sure *what* force you're talking about, but I'll take your word for it. And while I'm at it, the next time you throw a dart, I sure hope it at least hits the dart-board - there's nothing more uncomfortable than having to apologise to an unknown, uninterested, and uninvolved bystander who has a dart sticking out of his forehead just for having been in the room. But for what it's worth, oh don't be silly, no apology necessary. :-) If there is demand for job offer postings, then these should be handled on a separate mailing list. If you say so, I never really liked playing darts anyway, stupid game - too many people holding sharp instruments they have too little control over. Cheers, Geoff
how to get individual patches
Grant Likely wrote: On 7/14/06, David H. Lynch Jr. dhlii at dlasys.net wrote: AFAIK, yes you will have to repatch every time; I typically write a little helper script to lessen the pain: git bisect good|bad # depends on whether it works or not patch [patchfile] compile, test, etc cg restore -f # Remove the patches git bisect good|bad # lather, rinse, repeate Alright, I have bisected my way down to the problem. Well sort of. I think the real problem I started looking for eventually got fixed in the kernel tree on its own. But I did find a real problem. I have found my own work around - but this problem may effect others. The zlib library was updated within the past month. The new zlib code does not work in my environment. I have guesses as to why, but I am not a zlib expert and not looking to be one. I have solved my personal problem by reverting to the older zlib code. With that I have 2.6.18-rc4 or whatever is in the linux-2.6 git tree as of today working for me. I was stuck at 2.6.16.21 before. So my questions: How/where do I report a problem ? I would be perfectly happy to help whoever is responsible for zlib to work this out. But I am not up to doing it myself. git bisect got me down to a good/bad scenario. But I could not provoke git to either pull the offending patch or export the change as a patch so that I could back it out myself. Now that the final git bisect screen is gone all I have (besides a fixed 2.6.18-xx kernel) is I guess the sha has number for the particular commit. I suspect that would have been enough to yank just that patch but I googled every permutation of git backout or similar things I could think of and browsed the git tutorials etc. and could not seem to decipher how to do anything usefull with the sha id of a single patch. I am sure that is a knowledge problem. -- Dave Lynch DLA Systems Software Development:Embedded Linux 717.627.3770 dhlii at dlasys.nethttp://www.dlasys.net fax: 1.253.369.9244Cell: 1.717.587.7774 Over 25 years' experience in platforms, languages, and technologies too numerous to list. Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction. Albert Einstein
how to get individual patches
On 7/16/06, David H. Lynch Jr. dhlii at dlasys.net wrote: The zlib library was updated within the past month. The new zlib code does not work in my environment. I have guesses as to why, but I am not a zlib expert and not looking to be one. I have solved my personal problem by reverting to the older zlib code. With that I have 2.6.18-rc4 or whatever is in the linux-2.6 git tree as of today working for me. I was stuck at 2.6.16.21 before. So my questions: How/where do I report a problem ? I would be perfectly happy to help whoever is responsible for zlib to work this out. But I am not up to doing it myself. Once you've got the patch extracted (see below); post it to the lkml with a description of your symptoms and what you are trying to do. (or post it here, and if nobody knows; then move over to the lkml) git bisect got me down to a good/bad scenario. But I could not provoke git to either pull the offending patch or export the change as a patch so that I could back it out myself. Now that the final git bisect screen is gone all I have (besides a fixed 2.6.18-xx kernel) is I guess the sha has number for the particular commit. git-format-patch good_sha1..bad_sha1 for example: $ git-format-patch 0ce030395b92270567423d57d9d432eb77df32f2..8d92bc2270d67a43b1d7e94a8cb6f81f1435fe9a 0001-PCI-Error-handling-on-PCI-device-resume.txt extracts a single patch file for the PCI-Error-handling-on-PCI-device-resume.txt commit. If there are more than one commits between good_sha1 and bad_sha1, then you'll get more than one patch file extracted. Then, you can apply the patch reversed to backout the change. I suspect that would have been enough to yank just that patch but I googled every permutation of git backout or similar things I could think of and browsed the git tutorials etc. and could not seem to decipher how to do anything usefull with the sha id of a single patch. git-log sha1 will give you the history starting at a particular commit, which is useful for finding the next commit after it for doing the git-format-patch command. Cheers, g. -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. grant.likely at secretlab.ca (403) 399-0195
uboot environment variables size for Yosemite board.
In message FAB00A8DC59FAB42B13C2B3B0F6877010D14478B at ehost011-3.exch011.intermedia.net you wrote: I'm using uboot-1.1.4 for AMCC PPC440E Yosemite board. I've downloaded Note that this is off topic here. You should have posted this on the U-Boot-Users mailing list instead. this uboot from DENX site. It uses EEPROM to store environment variables. Since EEPROM on Yosemite board is only 512 bytes, there can not be more environment variables which is not very convenient. Thisi s wrong. The Yosemite configuration uses (like most (all?) AMCC eval boards - two redundand flash sectors to store the environment. And available environment size is 8 kB: = print ... Environment size: 1355/8187 bytes There is theoretical possibility to save these variables on flash (64M from which I use only part) and yosemite.h header file even has defines, allowing this option. But is it going work in reality? What is simplest way for Yosemite board to increase environment variables storage space? I have no idea where you got your board configuration from, but it is definitely not current code, nor the binary imageat ftp://ftp.denx.de/pub/u-boot/images/amcc/yosemite/u-boot.bin The current code does use (redundand) flash for environment storage. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de The idea of male and female are universal constants. -- Kirk, Metamorphosis, stardate 3219.8
What is request_module: runaway loop modprobe binfmt-4c46?
# # CONFIG_I2C is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Hardware Monitoring support # # CONFIG_HWMON is not set # CONFIG_HWMON_VID is not set # # Misc devices # # # Multimedia Capabilities Port drivers # # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # Digital Video Broadcasting Devices # # CONFIG_DVB is not set # # Graphics support # # CONFIG_FB is not set # # Console display driver support # CONFIG_DUMMY_CONSOLE=y # # Sound # # CONFIG_SOUND is not set # # USB support # # CONFIG_USB_ARCH_HAS_HCD is not set # CONFIG_USB_ARCH_HAS_OHCI is not set # # NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' # # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # # SN Devices # # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y # CONFIG_EXT2_FS_SECURITY is not set CONFIG_EXT2_FS_XIP=y CONFIG_FS_XIP=y # CONFIG_EXT3_FS is not set # CONFIG_JBD is not set CONFIG_FS_MBCACHE=y # CONFIG_REISERFS_FS is not set # CONFIG_JFS_FS is not set CONFIG_FS_POSIX_ACL=y # CONFIG_XFS_FS is not set # CONFIG_MINIX_FS is not set # CONFIG_ROMFS_FS is not set # CONFIG_INOTIFY is not set # CONFIG_QUOTA is not set CONFIG_DNOTIFY=y CONFIG_AUTOFS_FS=y CONFIG_AUTOFS4_FS=y # CONFIG_FUSE_FS is not set # # CD-ROM/DVD Filesystems # # CONFIG_ISO9660_FS is not set # CONFIG_UDF_FS is not set # # DOS/FAT/NT Filesystems # # CONFIG_MSDOS_FS is not set # CONFIG_VFAT_FS is not set # CONFIG_NTFS_FS is not set # # Pseudo filesystems # CONFIG_PROC_FS=y # CONFIG_PROC_KCORE is not set CONFIG_SYSFS=y CONFIG_TMPFS=y # CONFIG_HUGETLB_PAGE is not set CONFIG_RAMFS=y # CONFIG_RELAYFS_FS is not set # # Miscellaneous filesystems # # CONFIG_ADFS_FS is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BFS_FS is not set # CONFIG_EFS_FS is not set # CONFIG_CRAMFS is not set # CONFIG_VXFS_FS is not set # CONFIG_HPFS_FS is not set # CONFIG_QNX4FS_FS is not set # CONFIG_SYSV_FS is not set # CONFIG_UFS_FS is not set # # Network File Systems # CONFIG_NFS_FS=y CONFIG_NFS_V3=y CONFIG_NFS_V3_ACL=y CONFIG_NFS_V4=y CONFIG_NFS_DIRECTIO=y # CONFIG_NFSD is not set CONFIG_ROOT_NFS=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y CONFIG_NFS_ACL_SUPPORT=y CONFIG_NFS_COMMON=y CONFIG_SUNRPC=y CONFIG_SUNRPC_GSS=y CONFIG_RPCSEC_GSS_KRB5=y # CONFIG_RPCSEC_GSS_SPKM3 is not set # CONFIG_SMB_FS is not set # CONFIG_CIFS is not set # CONFIG_NCP_FS is not set # CONFIG_CODA_FS is not set # CONFIG_AFS_FS is not set # CONFIG_9P_FS is not set # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # # Native Language Support # # CONFIG_NLS is not set # # IBM 40x options # # # Library routines # # CONFIG_CRC_CCITT is not set # CONFIG_CRC16 is not set CONFIG_CRC32=y # CONFIG_LIBCRC32C is not set # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y # CONFIG_MAGIC_SYSRQ is not set CONFIG_LOG_BUF_SHIFT=14 # CONFIG_DETECT_SOFTLOCKUP is not set # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_INFO is not set # CONFIG_DEBUG_FS is not set # CONFIG_DEBUG_VM is not set # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_KGDB is not set # CONFIG_XMON is not set CONFIG_BDI_SWITCH=y CONFIG_SERIAL_TEXT_DEBUG=y CONFIG_PPC_OCP=y # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y # CONFIG_CRYPTO_HMAC is not set # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=y # CONFIG_CRYPTO_SHA1 is not set # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=y # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set # CONFIG_CRYPTO_DEFLATE is not set # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # Zhou Rui Distributed Embedded System Lab School of Information Science Engineering Lanzhou University, P. R. China http://dslab.lzu.edu.cn/~zr/ - -3.5G???20M??? -- next part -- An HTML attachment was scrubbed... URL: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060717/186c203a/attachment.htm
uboot environment variables size for Yosemite board.
Wolfgang Denk wrote: In message FAB00A8DC59FAB42B13C2B3B0F6877010D14478B at ehost011-3.exch011.intermedia.net you wrote: I'm using uboot-1.1.4 for AMCC PPC440E Yosemite board. I've downloaded Note that this is off topic here. You should have posted this on the U-Boot-Users mailing list instead. this uboot from DENX site. It uses EEPROM to store environment variables. Since EEPROM on Yosemite board is only 512 bytes, there can not be more environment variables which is not very convenient. Thisi s wrong. The Yosemite configuration uses (like most (all?) AMCC eval boards - two redundand flash sectors to store the environment. And available environment size is 8 kB: He has an older Yosemite. The original Yosemite U-Boot used the EEPROM for environment variables. = print ... Environment size: 1355/8187 bytes There is theoretical possibility to save these variables on flash (64M from which I use only part) and yosemite.h header file even has defines, allowing this option. But is it going work in reality? What is simplest way for Yosemite board to increase environment variables storage space? I have no idea where you got your board configuration from, but it is definitely not current code, nor the binary imageat ftp://ftp.denx.de/pub/u-boot/images/amcc/yosemite/u-boot.bin The current code does use (redundand) flash for environment storage. Best regards, Wolfgang Denk
XUP Linux Envirnment, Hi Everyone!
Hey list, I'm new here so I thought I'd introduce myself a bit. I'm a grad
student at the University of Colorado Boulder, and am researching novel FPGA
reconfiguration techniques this summer. Our focus is on Xilinx parts and their
partial reconfiguration features. Our goal is to use active reconfiguration to
move functional blocks around an FPGA as needed for space-based mission
survivability.
Anyway, in order to do this I first need to get a Linux envirnment up and
running on my Xilinx XUP board. This board has a Virtex II Pro FPGA with dual
PPC405 cores built-in. I have a basic Linux install built up using the EMPART
tutorial (http://www.cs.washington.edu/research/lis/empart/xup_ppc_linux.shtml)
and other pages it references. I have followed these instructions exactly,
including busybox and Linux kernel versions (1.1.0 and 2.4.26, respectively)
and everything looks swell EXCEPT: I can't manage to communicate with my
custom IP hanging off the OPB bus. Actually, I can't manage to communicate
with any peripherals at all off the OPB bus.
As per the EMPART tutorial's recommendations, here's how I attempt IP access:
fd = open(/dev/mem, O_RDWR);
ptr = MAP_FAILED; // Initialize to bad value
ptr = (int *) mmap(0, 256, PROT_READ|PROT_WRITE, MAP_SHARED, fd,
USER_LOGIC_BASEADDR);
if(ptr==MAP_FAILED) {
printf(Err: cannot access address!\n);
return -1;
}
*ptr = 0xA;
The mmap call appears to work, and returns a pointer to virtual memory that
supposedly references the physical address my IP is located at. However, when
I try to read or write to this pointer I just get a rather ambiguous bus
error.
Some random things I have tried:
- setting dugging for devfs
- returns no unusual messages
- numerous scans through kernel config params looking for some sort of MMU
settings or something
- setting a pointer directly to the physical address of the peripheral
- yeah, right...
- mapping a pointer to another established IP, in this case UART
- same problem
Anyone have any experience with this topic? Any suggestions at all? Do you
think it has something to do w/ the MMU of the PPC405, or am I way off base
here? I know this isn't an FPGA forum, but then I don't think there exists a
forum which exactly meets my needs. :)
Thanks much, --scott
-- next part --
An HTML attachment was scrubbed...
URL:
http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20060717/ff26fe69/attachment.htm
where is the kernel source for ppc embedded?(may sound stupid)
Hi: I am taking another guys porting work, he downloaded 2.4.30 for ppc. I was looking at http://www.denx.de/, and kernel.org, didn't feel like it was from there, since the current source tree only have arch/ppc directory, no other arch specific tree. So where i should download 2.4.30 with all patch applied? Thanks ls
where is the kernel source for ppc embedded?(may sound stupid)
On 7/17/06, Lei Sun leisun124 at gmail.com wrote: Hi: I am taking another guys porting work, he downloaded 2.4.30 for ppc. I was looking at http://www.denx.de/, and kernel.org, didn't feel like it was from there, since the current source tree only have arch/ppc directory, no other arch specific tree. So where i should download 2.4.30 with all patch applied? http://penguinppc.org/kernel/ -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. grant.likely at secretlab.ca (403) 399-0195
where is the kernel source for ppc embedded?(may sound stupid)
I looked at that website, and it suggested downloading kernel from kernel.org. I've downloaded , but apparently, it's different with what I have right now, there is no ADS8260 and PQ2FADS-VR board type . I think there are some patch for that board already, where can I find those patches? Thanks ls On 7/17/06, Grant Likely grant.likely at secretlab.ca wrote: On 7/17/06, Lei Sun leisun124 at gmail.com wrote: Hi: I am taking another guys porting work, he downloaded 2.4.30 for ppc. I was looking at http://www.denx.de/, and kernel.org, didn't feel like it was from there, since the current source tree only have arch/ppc directory, no other arch specific tree. So where i should download 2.4.30 with all patch applied? http://penguinppc.org/kernel/ -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. grant.likely at secretlab.ca (403) 399-0195
where is the kernel source for ppc embedded?(may sound stupid)
On 7/17/06, Lei Sun leisun124 at gmail.com wrote: I looked at that website, and it suggested downloading kernel from kernel.org. I've downloaded , but apparently, it's different with what I have right now, there is no ADS8260 and PQ2FADS-VR board type . I think there are some patch for that board already, where can I find those patches? Try the no longer used tree listed at the bottom of the page if you want a 2.4 kernel. If you want 2.6, use kernel.org I don't know if ADS8260 or PQ2FADS-VR support is in either tree. g. -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. grant.likely at secretlab.ca (403) 399-0195
