Re: Serial console not working on EP8343M
On Mar 12, 2007, at 10:05 PM, Ed Swierk wrote: I'm having trouble getting the serial console to work on an EP8343M board when using U-Boot 1.2.0 to start Linux 2.6.20.1. I'm using arch powerpc and platform MPC834x_SYS (which is perhaps wishful thinking, as my board is different, although it should at least have the same serial port configuration). The symptoms are exactly the same as those in http://ozlabs.org/pipermail/linuxppc-embedded/2006-September/ 024457.html: the console stops working after the call to console_init(). The suggested solution was to ensure that U-Boot is setting timebase-frequency, bus-frequency and clock-frequency and passing those properties to the kernel, and this does indeed seem to be happening in my case. I've attached the output from U-Boot (including a dump of the flat device tree), as well as my kernel config and U-Boot board settings. Any help would be appreciated. --Ed Have you tried make the bootargs just console=ttyS0,115200 (or whatever your baud rate is)? - k ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Problem initialising PCI device
I am working with a MEN A14C board (PPC 8540), and I am trying to get a
Reflective Memory card (VMIC 5565) working in one of the PMC slots
using Linux (ELinOS).
When I load the driver I am able to access the registers of the card
using the pci access routines (pci_read_config_word, etc.), but when I
try to access the registers or the memory on the card using memory
mapped access this does not work.
The PMC bus is separated from the main PCI bus by a PCI-PCI bridge (Hint
Corp HB2 PCI-PCI Bridge (rev 04), vendor 0x3388, device 0x0026). For
some other devices (that are connected directly to the PCI bus) I don't
have any problems accessing the memory directly.
Am I forgetting something, or is there something else wrong here?
Below is the code I use to access the reflective memory card (this code
is cut from the _init_one function):
pci_enable_device(dev);
err = pci_request_regions(dev, RFM);
if (err != 0) {
os_print(OS_ERR Cannot obtain PCI resources\n);
return( -ENOMEM );
}
/* Get the physical address of the local and runtime registers */
unit-physAddrOr = pci_resource_start(dev, 0);
data-orRegs = ioremap_nocache(unit-physAddrOr, 0x40);
/* Get the physical address of the control and status registers */
unit-physAddrCs = pci_resource_start(dev, 2);
data-csRegs = ioremap_nocache(unit-physAddrCs, 0x40);
printk(KERN_ERR OR: %8.8x, CS: %8.8x\n, unit-physAddrOr,
unit-physAddrCs);
printk(KERN_ERR OR: %8.8x, CS: %8.8x\n, data-orRegs, data-csRegs);
for(i = 0; i 4; i++)
{
printk( KERN_ERR%2.2x: %8.8x\n, i, os_readl(data-csRegs + i*4));
}
The code above generates the following output:
OR: de00, CS: ddc0
OR: e106ae00, CS: e106cdc0
00: 86000300
01: 86000300
02: 86000300
03: 86000300
I would expect the data from the card, as reported by lspci. So instead
of 00: 86000300 I would expect something like 00:5565114a, which is
the ident of the card.
Thank you for your time and (hopefully) your answer.
Kind regard,
Johan Borkhuis
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
gcc -static
Hello all, Can any body tell me what is the use of - static option for gcc compilation ? Nirav J Patel M.Tech(CSE), Nirma University, Ahmedabad-382481. 9925138959 - Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games.___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Serial console not working on EP8343M
On 3/13/07, Kumar Gala [EMAIL PROTECTED] wrote: Have you tried make the bootargs just console=ttyS0,115200 (or whatever your baud rate is)? I've tried that too. I just stepped through most of the console_initcall sequence with gdb and it seems like everything is getting set up properly, including irq and mmio settings for the serial devices, but still nothing gets printed. Maybe interrupts aren't getting routed? I just discovered the udbg-immortal command line option, which prevents console_init from optimistically disabling the udbg console. Debugging this problem should be a lot easier now that I can see console output past console_init. --Ed ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: Problem in compiling a kernel module
On 14/03/07 05:33 +0100, Matthias Fechner wrote:
Hello Ben,
* Ben Warren [EMAIL PROTECTED] [13-03-07 05:55]:
Is there any chance that you qualify private data as
__init within the driver? Can you post the cleanup()
function and any private (static) functions that it
calls?
no problem, I attached the file. It is bery basic from now and it is
not written very well, but it should have all necessary parts in it.
PS: It's not necessary to CC me I'm on the list :)
...
static int __initdata max6633_initialized = 0;
__initdata
void max6633_cleanup(void)
{
int res;
if(max6633_initialized==1)
But you access it from non-init code.
Domen
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
