Can please somebody tell me what could be the reason for the following error (Unix Motorola Server):
/usr/etc/ce3/s374: Board at address 0xff10000 not present - Entry skipped.
/dev/lpc2: I/O error
I already replaced the board 374 on the server, but I have the same problem.
Thank you! (1 Reply)
HI all,
I have armv7 board and i will execute script in host machine with ssh connection from board .
I have to test when board in standby mode the script runned in host remain working .
The result is the reverse when kernel is in standby mode on board.
SSH connection closed and the... (3 Replies)
Discussion started by: marwen_joe
3 Replies
3. Post Here to Contact Site Administrators and Moderators
Just a remark now the board has grown to considerable proportion. I see too little of an active hand(s) maintaning the boards, clipping away dead posts, moving posts that were created in the wrong forums etc. It's a bit tiring to see alot of threads ending in: this has been covered before, do a... (7 Replies)
I2C_REGISTER_BOARD_I(9) I2C and SMBus Subsystem I2C_REGISTER_BOARD_I(9)NAME
i2c_register_board_info - statically declare I2C devices
SYNOPSIS
int i2c_register_board_info(int busnum, struct i2c_board_info const * info, unsigned len);
ARGUMENTS
busnum
identifies the bus to which these devices belong
info
vector of i2c device descriptors
len
how many descriptors in the vector; may be zero to reserve the specified bus number.
DESCRIPTION
Systems using the Linux I2C driver stack can declare tables of board info while they initialize. This should be done in board-specific init
code near arch_initcall time, or equivalent, before any I2C adapter driver is registered. For example, mainboard init code could define
several devices, as could the init code for each daughtercard in a board stack.
The I2C devices will be created later, after the adapter for the relevant bus has been registered. After that moment, standard driver model
tools are used to bind "new style" I2C drivers to the devices. The bus number for any device declared using this routine is not available
for dynamic allocation.
The board info passed can safely be __initdata, but be careful of embedded pointers (for platform_data, functions, etc) since that won't be
copied.
COPYRIGHT Kernel Hackers Manual 2.6. July 2010 I2C_REGISTER_BOARD_I(9)