Question about modules
In message <20030303221205.GA12414 at ip68-0-152-218.tc.ph.cox.net> you wrote: > > > In commproc.c, add the following line: > > EXPORT_SYMBOL(m8xx_cpm_hostalloc); > > I'll bite... Dan is there a good reason this isn't exported? Google > shows nothing to me :) IMHO the only "good" reason they were not exported right from the beginnng is that the standard drivers that come with the kernel tree cannot be built as modules anyway, so nobody needed it. Please add. Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de A Perl script is correct if it's halfway readable and gets the job done before your boss fires you. - L. Wall & R. L. Schwartz, _Programming Perl_ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
"printk" does not print
After setting up the right log level, printk now works! many thanks to all Gianfranco - Original Message - From: "Mark Hatle" <[EMAIL PROTECTED]> To: "Stephan Linke" Cc: "Bret Indrelee" ; "Linuxppc-Embedded" Sent: Monday, March 03, 2003 5:38 PM Subject: Re: "printk" does not print > > Stephan Linke wrote: > > Hi, > > > > if your startup skript changes the console log level in /proc/sys/kernel/printk maybe not all messages are displayed on console. But > > you can still look into /var/log/messages. > > ...assuming you have klogd/syslogd installed and running... > > --Mark > > > Regards, Stephan > > > > > >>-Original Message- > >>From: owner-linuxppc-embedded at lists.linuxppc.org > >>[mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Bret > >>Indrelee > >>Sent: Montag, 3. Marz 2003 15:46 > >>To: Ing.Gianfranco Morandi > >>Cc: LinuxPPC > >>Subject: Re: "printk" does not print > >> > >> > >> > >>On Mon, 3 Mar 2003, Ing.Gianfranco Morandi wrote: > >> > >>>Hi to all, > >>> > >>>I'm trying to trace the execution path of a custom ISDN driver, and I have > >>>used some printk() instructions to give some messages out. > >>> > >>>Now, everything is going well, but when I try to open the ttyI0 device (or > >>>ttyIx it is the same) the printk() that I have placed into the file > >>>isdn_tty.c does not print any messages. I am sure that such procedure has > >>>been executed because I have placed a breakpoint on the "isdn_tty_open()" > >>>and the program stopped. > >>> > >>>Anybody has an idea what happens? > >> > >>You probably neglected to set a KERN_ level. > >> > >>See if they are in your dmesg or messages file, you might be sending them > >>to syslog but not the screen. > >> > >>-Bret > >> > >>-- > >>Bret Indrelee QLogic Corporation > >>Bret.Indrelee at qlogic.com 6321 Bury Drive, St 13, Eden Prairie, MN 55346 > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PCI support for MPC8250
We are developing a system around the MPC8250 and will use the internal PCI. Last december there was a thread on this mailinglist for PCI support for the MPC8265/6 (which is similar for the MPC8250?). Scanning through the linuxppc_2.4 development tree (2.4.20) did no show support for this. Is this PCI devices already included in the bitkeeper development tree? -- willy ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Serial Console disable/enable dynamically
Hi All I have an custom board which has PPC 440GP as its processor. I have build a kernel image and ramdisk to run on the custom board, which is running fine.There is only one serial port in the board. This serial port is used as the serial console. I wanted to disable and enable the serial console dynamically, whenever the serial console is disabled , I want to use the serial port for other purposes. Can anybody suggest how to disable and enable dynamically?. Thanking you in advance Regards Aman ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK Problem
hello, As suggested, i downloaded the "simple-ramdisk.PPCBoot" from ftp site and also went thru the dplg.pdf file to know more about PPCBoot. Iam working on MPC8260ADS and trying to boot linux-2.4.1 in a standalone mode without NFS support. I loaded both kernel image which was booting earlier with NFS system and newly downloaded ramdisk at address 10 and 20 respectively. And i also updated the bootargs environment variable as --- setenv bootargs root=/dev/ram ip=10.1.40.176:10.1.40.175:10.1.1.1:255.255.0.0:10.1.40.175::off --- where, target ip = 10.1.40.176 server ip = 10.1.40.175 gateway ip = 10.1.1.1 netmask = 255.255.0.0 host name = 10.1.40.175 I have checked ip addresses for correctness. After all this, i gave bootm 10 20 command. Output: After loading kernel image and ramdisk image, it is hanging!!! --- Messages --- ## Booting Linux kernel at 1010 ... Image Name: Linux-2.4.1 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 400259 Bytes = 390 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 1020 ... Image Name: Simple Ramdisk Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 507630 Bytes = 495 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 00ed4000, end 00f5eab4 ... OK [After this, no messages] --- Messages --- I am stuck at this point and don't know what could be the reason. Can somebody help me? thanks in advance, with rgds, kamal ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
PrPMC800 NON-MONARCH Patch
Finally I have a working PrPMC800 Linux for NON-MONARCH operations. The
attached patch is what is needed.
The content of the patch falls in three categories:
1. PrPMC800 specific stuff (in files prpmc*, harrier*)
2. Discontigous memory support (various files) and a gross hack in
numa.c
3. Making all network and PCI memory DMA-able, I did the changes at
this low level since I found numerous places where GFP_DMA should
be added to get things working, and on most systems all (or much)
of the memory is DMA-able, thus nobody has experienced any problems
before (arch/ppc/kernel/pci-dma.c, net/core/skbuff.c)
IMHO, supporting systems where DMA-able memory is small and not starting in
low memory is harder than it needs to be (and wastes memory, since memory
zones needs to be 2MB aligned). I think it would be easier to describe
memory layout with something like:
typedef struct {
void *start;
unsigned long size;
gfp_type kind;
} memory_layout_t;
memory_layout_t the_memory_layout = {
{ 0, 0x400, GFP_NORMAL },
{ 0x400, 0x10, GFP_DMA },
...
than it is to describe it as a number of memory nodes, each consisting of
GFP_NORMAL, GFP_DMA and GFP_HIGHMEM memory, and their associated holes to
make everything align to 2 MB (1 << PAGE_SHIFT << (MAX_ORDER -1))
Patch is available as:
http://www.control.lth.se/~andersb/prpmc800/2003-03-03.patch
and something somewhat like ChangeLog entries is available as:
http://www.control.lth.se/~andersb/prpmc800/patch_2003-03-03_description.
txt
Regards
Anders Blomdell
--
Anders Blomdell
Department of Automatic ControlEmail: anders.blomdell at control.lth.
se
Lund Institute of Technology Phone: +46 46 222 4625
Box 118, S-221 00 Lund, Sweden Fax: +46 46 138118
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
SCC3 UART for MPC850
Donald MacArthur wrote: > I am currently working with an embedded planet LICCE MPC850 Credit card > board ... > ...Does anyone know of modifications required for the kernel > to get SCC3 to work as a UART or were possible conflicts might arise? There are several things that may need attention. First, ensure the version of the 850 you have actually has the SCC3 port. Second, as in many cases, the SCC3 pins are multiplexed with other uses. In this case you have to program the I/O so they are used for SCC3 instead of SPI and other functions. Third, if you are using one of the matching Embedded Planet I/O cards, ensure the board control register has been written to enable/route the driver. If you are using the Embedded Planet I/O card, check the documentation for the specific card to ensure you can enable all of the serial ports. In some cases not all combinations are supported. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
"printk" does not print
Hi, if your startup skript changes the console log level in /proc/sys/kernel/printk maybe not all messages are displayed on console. But you can still look into /var/log/messages. Regards, Stephan > -Original Message- > From: owner-linuxppc-embedded at lists.linuxppc.org > [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Bret > Indrelee > Sent: Montag, 3. Marz 2003 15:46 > To: Ing.Gianfranco Morandi > Cc: LinuxPPC > Subject: Re: "printk" does not print > > > > On Mon, 3 Mar 2003, Ing.Gianfranco Morandi wrote: > > Hi to all, > > > > I'm trying to trace the execution path of a custom ISDN driver, and I have > > used some printk() instructions to give some messages out. > > > > Now, everything is going well, but when I try to open the ttyI0 device (or > > ttyIx it is the same) the printk() that I have placed into the file > > isdn_tty.c does not print any messages. I am sure that such procedure has > > been executed because I have placed a breakpoint on the "isdn_tty_open()" > > and the program stopped. > > > > Anybody has an idea what happens? > > You probably neglected to set a KERN_ level. > > See if they are in your dmesg or messages file, you might be sending them > to syslog but not the screen. > > -Bret > > -- > Bret Indrelee QLogic Corporation > Bret.Indrelee at qlogic.com 6321 Bury Drive, St 13, Eden Prairie, MN > 55346 > > > > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Linux console on virtual Uart?
Hello, I'm porting Denx linux 2.4.4 to my company MPC8260 board. The board doesn't have the real UART to be configured as ttyS0. It has a virtual UART (a memory location where characters are read/written from/to. Another processor will take care of UART translation.) I haved modified uart.c to provide basic serial i/o functions using the virtual uart. When running with NFS root filesystem, I got this: ---Message-- modprobe: modprobe: Can't locate module char-major-4 INIT: version 2.78 booting Welcome to DENX Embedded Linux Environment Press 'I' to enter interactive startup. Mounting proc filesystem: [ OK ] Configuring kernel parameters: [ OK ] Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Setting clock : Wed Dec 31 19:00:20 EST 1969 [ OK ] Activating swap partitions:[ OK ] Setting hostname bdevppc01:[ OK ] Finding module dependencies: [ OK ] Checking filesystems [ OK ] Mounting local filesystems:[ OK ] Enabling swap space: [ OK ] INIT: Entering runlevel: 3 Entering non-interactive startup Starting system logger:[ OK ] Starting kernel logger:[ OK ] Starting xinetd: [ OK ] bdevppc01 login: root Last login: Wed Dec 31 19:02:17 on console ---Message-- There is no shell prompt?? Using telnet, I can look at ps: ---Message-- root 161 1 0 19:01 ttyS000:00:00 login -- root root 162 155 0 19:01 ?00:00:00 in.telnetd: 172.30.254.69 root 163 162 1 19:01 ttyp000:00:00 login -- root root 164 163 2 19:01 ttyp000:00:01 -bash root 189 161 89 19:02 ttyS000:00:27 -bash ---Message-- When running with ramdisk, I got this: ---Message-- bash# ls bin dev etc lib linuxrc lost+found bash# asdf init: asdf: command not found bash# ---Message-- Why "init:" is printed out in "init: asdf: command not found"?. Probably some variables didn't get initialized properly? Does anyone know where is the problem? thanks in advance james ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
register_serial on 405 platform
Hi, I need to register some non-standard serial 16550 UART ports on a 405GP platform. I noticed that the rs_table in drivers/char/serial.c has only two entries (used by the on-chip serial ports). So I cannot understand how I can register further ports without changing the kernel source. Am I right, that it is currently not possible to register further serial ports with the 2_4_devel tree on 405 platforms? Matthias ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Improved copy_page() function, about 30% speed up for mpc860!
Joakim Tjernlund wrote: > I have been playing with the copy_page() function in arch/ppc/kernel/misc.S > and gained about 30% speed up for my mpc860, rev D4 MHz. Have you found the discussion in linuxppc-dev about the work Paul has done on this in general for PowerPC? It may help avoid repeating some work and provide some guidance. And don't forgetmany applications aren't heavily 'copy-centric' and it may be beneficial to not blow away the caches in those cases. That is, if you apply systems engineering methods to your testing instead of just focusing on such a low level detail, you may discover you are wasting your time and from an overall system application you may be providing little benefit or even a overall degradation in system performance. Thanks. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Calling __eabi
Despite compiling with;
powerpc-linux-gcc -Iinclude -g -meabi -c -o obj/app_init.o app_init.c
the expected compiler-generated call to __eabi() is not magically inserted
at the start of main. (Using powerpc-linux-gcc version 2.95.3)
Have I perhaps misinterpreted the following in the GNU CC Manual?:
>>>
Selecting -meabi means that the stack is aligned to an 8 byte boundary, a
function __eabi is called to from main to set up the eabi environment, and the
`-msdata' option can use both r2 and r13 to point to two separate small data
areas.
<<<
And in Motorola's AN1809:
>>>
Much of the required EABI register setup is accomplished through a call to
__eabi(). The user does not call this function directly. Instead, the
compiler inserts the call to __eabi() at the beginning of main() in the user
program.
<<<
From an objdump of the object file:
>>>
int main(void)^M
{^M
104258: 94 21 ff f0stwu r1,-16(r1)
10425c: 7c 08 02 a6mflr r0
104260: 93 e1 00 0cstw r31,12(r1)
104264: 90 01 00 14stw r0,20(r1)
104268: 7c 3f 0b 78mr r31,r1
init_led(); // Whoof! Into it, but no __eabi!?
10426c: 48 00 07 89bl 1049f4
<<<
There's sommat else that needs to be done, to tickle it into
delivering the goods, and I haven't twigged to it yet.
Regards,
Erik
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Status of 2.5 for 8xx?
Pantelis Antoniou wrote: > How is the status of 2.5 for 8xx? Sorry, I've been travelling for the past week without computer. I'm back now and working on it again. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Problem porting 2.4.17 linux to MPC8260ADS
Kamalesh B wrote: > [KAMAL]: > All memory mapping is handled correctly. > SDRAM is mapped to 0xC000 from 0x > Flash is mapped to 0xFF80 from 0xFF80 > Board control/status register is mapped to 0xF010 from 0x0450 > IMMR is mapped to 0xF000 from 0x0470 > > Iam using BATs to do this (BAT0 and BAT1) If I understand correctly (and I may not), this isn't being done correctly. Linux is going to take over the BATs for it's own mapping. It doesn't matter what you have set in them. You must ensure the IMMR is physically mapped to 0xf000. That is, you have to change the IMMR register to this value, you can't use a BAT to map this value to the virtual 0xf000 and then call Linux. The SDRAM will be remapped by Linux to use the BAT 3/4 registers based upon how much memory you tell it is available in the board descriptor structure. The Flash and board control register will have to be mapped using ioremap() and you will have to use the subsequent returned virtual address to access these regions. > [KAMAL]: > After turning on MMU, iam using the LED code to flash leds and it is > working. Memory map of board control status register after turning on MMU is > 0xf010. Only at this point it won't. No, they are not mapped there. The only thing Linux knows about early in the kernel is a small portion of the ram. Linux completely changes the MMU mapping, it doesn't matter what you have mapped when you call the kernel. Your board control registers are not mapped any longer shortly after you call the Linux kernel. > [KAMAL]: > Led flashing code looks something like this > --- Code begins --- > lis r20, 0xf010 > lis r21, 0 > stw r21, 0(r20) > --- Code ends --- That will crash the kernel shortly after you start it. -- Dan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
"printk" does not print
Hi to all, I'm trying to trace the execution path of a custom ISDN driver, and I have used some printk() instructions to give some messages out. Now, everything is going well, but when I try to open the ttyI0 device (or ttyIx it is the same) the printk() that I have placed into the file isdn_tty.c does not print any messages. I am sure that such procedure has been executed because I have placed a breakpoint on the "isdn_tty_open()" and the program stopped. Anybody has an idea what happens? many thanks Gianfranco ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Question about modules
On Fri, Feb 28, 2003 at 01:27:26PM -0500, Jean-Denis Boyer wrote: > > Everything works, till I try to insmod it: I get m8xx_cpm_alloc and > > m8xx_cpm_hostalloc as unresolved symbols. > > In commproc.c, add the following line: > EXPORT_SYMBOL(m8xx_cpm_hostalloc); I'll bite... Dan is there a good reason this isn't exported? Google shows nothing to me :) -- Tom Rini http://gate.crashing.org/~trini/ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
SCC3 UART for MPC850
In message you wrote: > > I am currently working with an embedded planet LICCE MPC850 Credit card > board with the associated MPC860 Timesys Linux Kernel. I would like to use > as many SCC and SMC channels for UARTs as possible. I have successfully > enabled SMC1, SMC2, and SCC2 for UART but SCC3 does not work. Normally for > the UART channels the TX lines go high when the kernel boots but the SCC3 Tx > channel does not. Does anyone know of modifications required for the kernel > to get SCC3 to work as a UART or were possible conflicts might arise? See the uart.c driver in the kernel source tree on our CVS server for support of serial ports on all SMC / SCC ports. Sorry, this is one of our patches that never was accepted for the official source trees (also including hardware flow control). Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de You have the capacity to learn from mistakes. You'll learn a lot today. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK Problem
In message <3E63484A.6340720C at tataelxsi.co.in> you wrote: > > Iam working on MPC8260ADS and trying to boot linux-2.4.1 in a standalone > mode without NFS support. 2.4 1. is very old. Did you make sure that the "clocks_in_mhz" variable is set in your PPCBoot environment? > I loaded both kernel image which was booting earlier with NFS system and I understand the NFS based kernel was working on your system? > newly downloaded ramdisk at address 10 and 20 respectively. And > i also updated the bootargs environment variable as > --- > setenv bootargs root=/dev/ram > ip=10.1.40.176:10.1.40.175:10.1.1.1:255.255.0.0:10.1.40.175::off > --- > > where, > target ip = 10.1.40.176 > server ip = 10.1.40.175 > gateway ip = 10.1.1.1 You should not configure a gateway address when you need none. > netmask = 255.255.0.0 > host name = 10.1.40.175 This is an IP address, but not a host name. [Not that teither of these would cause the boot to fail.] > Verifying Checksum ... OK > Loading Ramdisk to 00ed4000, end 00f5eab4 ... OK > > [After this, no messages] If your NFS based kernel was working correctly, you should at least see the same boot messages until it tires to mount the root filesystem. > I am stuck at this point and don't know what could be the reason. Can > somebody help me? Attach a debugger (BDI2000) and check where it's hanging. As a poor man's solution, try to find out if a post-mortem dump of the log_buf area contains some information: grep the System.map file in your kernel directory for the virtual address of "log_buf" and subtract 0xC000 to get the physical address; when you board hangs press the reset button and use PPCBoot's "md" command to print a memory dump of this area. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Put your Nose to the Grindstone! -- Amalgamated Plastic Surgeons and Toolmakers, Ltd. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
Xilinx PPC405 MHS file
Hello, Does anyone have an example of an MHS file for Xilinx PPC405 working with Linux? The ML300 port in the linuxppc_2_4_devel tree was apparently made using V2PDK, not EDK. Any and all information is appreciated. Thanks. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
"printk" does not print
Stephan Linke wrote: > Hi, > > if your startup skript changes the console log level in > /proc/sys/kernel/printk maybe not all messages are displayed on console. But > you can still look into /var/log/messages. ...assuming you have klogd/syslogd installed and running... --Mark > Regards, Stephan > > >>-Original Message- >>From: owner-linuxppc-embedded at lists.linuxppc.org >>[mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Bret >>Indrelee >>Sent: Montag, 3. Marz 2003 15:46 >>To: Ing.Gianfranco Morandi >>Cc: LinuxPPC >>Subject: Re: "printk" does not print >> >> >> >>On Mon, 3 Mar 2003, Ing.Gianfranco Morandi wrote: >> >>>Hi to all, >>> >>>I'm trying to trace the execution path of a custom ISDN driver, and I have >>>used some printk() instructions to give some messages out. >>> >>>Now, everything is going well, but when I try to open the ttyI0 device (or >>>ttyIx it is the same) the printk() that I have placed into the file >>>isdn_tty.c does not print any messages. I am sure that such procedure has >>>been executed because I have placed a breakpoint on the "isdn_tty_open()" >>>and the program stopped. >>> >>>Anybody has an idea what happens? >> >>You probably neglected to set a KERN_ level. >> >>See if they are in your dmesg or messages file, you might be sending them >>to syslog but not the screen. >> >>-Bret >> >>-- >>Bret Indrelee QLogic Corporation >>Bret.Indrelee at qlogic.com 6321 Bury Drive, St 13, Eden Prairie, MN >>55346 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
mvme 5500 board
Hi, I'm already using mvme 5100 boards. For an application I perhaps give a try to a 5500 board. Does somebody already use one under linux ? Since I'm running linux + rtai, I also ask the question about a mvme 5500 board with linux + rtai. xavier ps: I have a vme driver running quite well under 5100 and I will release it soon. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
SCC3 UART for MPC850
Are you sure that particular variant of the 850 processor has an SCC3? -Original Message- From: Donald MacArthur [mailto:[EMAIL PROTECTED] Sent: Monday, March 03, 2003 8:53 AM To: linuxppc-embedded at lists.linuxppc.org Subject: SCC3 UART for MPC850 I am currently working with an embedded planet LICCE MPC850 Credit card board with the associated MPC860 Timesys Linux Kernel. I would like to use as many SCC and SMC channels for UARTs as possible. I have successfully enabled SMC1, SMC2, and SCC2 for UART but SCC3 does not work. Normally for the UART channels the TX lines go high when the kernel boots but the SCC3 Tx channel does not. Does anyone know of modifications required for the kernel to get SCC3 to work as a UART or were possible conflicts might arise? Thank You Don MacArthur dmacarth at ufl.edu ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
SCC3 UART for MPC850
I am currently working with an embedded planet LICCE MPC850 Credit card board with the associated MPC860 Timesys Linux Kernel. I would like to use as many SCC and SMC channels for UARTs as possible. I have successfully enabled SMC1, SMC2, and SCC2 for UART but SCC3 does not work. Normally for the UART channels the TX lines go high when the kernel boots but the SCC3 Tx channel does not. Does anyone know of modifications required for the kernel to get SCC3 to work as a UART or were possible conflicts might arise? Thank You Don MacArthur dmacarth at ufl.edu ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
"printk" does not print
On Mon, 3 Mar 2003, Ing.Gianfranco Morandi wrote: > Hi to all, > > I'm trying to trace the execution path of a custom ISDN driver, and I have > used some printk() instructions to give some messages out. > > Now, everything is going well, but when I try to open the ttyI0 device (or > ttyIx it is the same) the printk() that I have placed into the file > isdn_tty.c does not print any messages. I am sure that such procedure has > been executed because I have placed a breakpoint on the "isdn_tty_open()" > and the program stopped. > > Anybody has an idea what happens? You probably neglected to set a KERN_ level. See if they are in your dmesg or messages file, you might be sending them to syslog but not the screen. -Bret -- Bret Indrelee QLogic Corporation Bret.Indrelee at qlogic.com 6321 Bury Drive, St 13, Eden Prairie, MN 55346 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
