<DIV>Thanks for your hint. But the file is just for Linux Kernel Version 2.6, is this also OK for me? (I am using a 2.4 kernel)</DIV> <DIV> </DIV> <DIV>But I doubt that same technique can be applied since the Bluetooth should only be enabled when I loaded the pcmcia drivers (pcmcia_core.o, m8xx_pcmcia.o and ds.o), so .... </DIV> <DIV> </DIV> <DIV>how can I pre-set some settings during boot-time that I have not yet insert the pcmcia modules into the kernel?</DIV> <DIV> </DIV> <DIV>Also the last thing is, since there is not "hotplug" in my system and resources allocation is different from standard PCs, so I cannot let my embedded system to auto-detect a standard uart has been added during the PCMCIA bluetooth card is plugged in (while standard PC will)</DIV> <DIV> </DIV> <DIV>or can anybody tell me that how can I realize hotplug in my system? (is this can be worked out?)</DIV> <DIV> </DIV> <DIV>Thanks<BR><BR><B><I>Vitaly Bordug
<vbordug@ru.mvista.com></I></B> 說：</DIV> <BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Lo Chun Chung wrote:<BR>> Dear all,<BR>> <BR>> I am a student from Hong Kong. Now I am doing a project about enabling a <BR>> Bluetooth PCMCIA card (Billionton PCBTC1A-B) in a custom MPC860PC.<BR>> <BR>> (The custom MPC860 system is constructed by a MPC860 Processor Card and <BR>> a custom made PCB to adding a PCMCIA interface to the processor Card.)<BR>> <BR>> Now my stage is: the LINUX (Linux Kernel 2.4.25 from ELDK 3.1 for <BR>> powerpc) can recognise the card by cardctl, and here are the screen dump:<BR>> <BR>> / # cardctl ident<BR>> Socket 0:<BR>> product info: "PCMCIA", "Bluetooth Card", "", ""<BR>> manfid: 0x0279, 0x950b<BR>> function: 2 (serial)<BR>> / # cardctl status<BR>> Socket 0:<BR>> 5V 16-bit PC Card<BR>> function 0: [ready], [bat dead], [bat low]<BR>> / #
cardctl info<BR>> PRODID_1="PCMCIA"<BR>> PRODID_2="Bluetooth Card"<BR>> PRODID_3=""<BR>> PRODID_4=""<BR>> MANFID=0279,950b<BR>> FUNCID=2<BR>> / # cardct! l config<BR>> Socket 0:<BR>> Vcc 5.0V Vpp1 5.0V Vpp2 5.0V<BR>> <BR>> but after I load all the modules needed (should be these?)<BR>> <BR>> / # lsmod<BR>> Module Size Used by Not tainted<BR>> hci_uart 14836 0 (unused)<BR>> l2cap 22956 0 (unused)<BR>> bluez 43856 0 [hci_uart l2cap]<BR>> ds 8060 0<BR>> m8xx_pcmcia 5164 1<BR>> pcmcia_core 39520 0 [ds m8xx_pcmcia]<BR>> <BR>> my bluetooth still cannot get working ...<BR>> <BR>> then I try to insert "serial_cs" as my bluetooth card is a uart base <BR>> card. but some message given out:<BR>> <BR>> / # insmod serial_cs<BR>> Using /lib/modules/2.4.25/serial_cs.o<BR>> insmod: unresolved symbol unregister_serial<BR>> insmod: unresolved symbol register_serial<BR>> <BR>> so I realize that I should
also insert "serial.o" into the linux, but <BR>> crashes ...<BR>> <BR>> / # insmod serial<BR>> Using /lib/modules/2.4.25/serial.o<BR>> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ enabled<BR>> Machine check in kernel mode.<BR>> Caused by (from SRR1=1032): Transfer error ack signal<BR>> ! Oops: machine check, sig: 7<BR>> NIP: C3040078 XER: 00000000 LR: C3044724 SP: C1CC1D60 REGS: c1cc1cb0 <BR>> TRAP: 0200 No<BR>> t tainted<BR>> MSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11<BR>> TASK = c1cc0000[33] 'busybox' Last syscall: 128<BR>> last math 00000000 last altivec 00000000<BR>> GPR00: 00000000 C1CC1D60 C1CC0000 C1CC1D70 00000004 00000001 00000B4B <BR>> C015378B<BR>> GPR08: 00000000 800003FC 00000003 C1CC1C70 C0170000 10084438 00000000 <BR>> 00000000<BR>> GPR16: 00000000 00000000 00000000 00000000 00009032 1016EDB0 C1D3A000 <BR>> C1CC1EA0<BR>> GPR24: C1F6B760 00000006 C304973C C1CC1D70 C3040000
00000000 00000000 <BR>> C3046348<BR>> Call backtrace:<BR>> C3044718 C3045188 C0012440 C00043BC 10080000 10021DF0 100238CC<BR>> 1000457C 100041A0 1000436C 1000457C 100041A0 0FE70EF4 00000000<BR>> <BR>> I only knows when i insert the serial.o, this driver will try to access <BR>> the standard uart which is not available in my system (my system only <BR>> has one uart by SMC1), then the system will crash eac! h time the <BR>> driver wants to access the registers does not available ...<BR>> <BR>> The project deadline is near ... so I ask here ...<BR>> <BR>> can anyone helps me or give me some clues?<BR>> <BR>You should take a look for instance how 8349 does this job (arch/ppc/syslib/ppc83xx_setup.c) - it also has "standard" UART, but some stuff needs to be set up<BR>prior to serial.o. Of course that is not complete solution for your case, just a hint...<BR>> Thanks all<BR>> <BR>> <BR>> <BR>> <BR>> Best regards,<BR>>
Chung<BR>> <BR>> _______________________________________<BR>> YM - 離線訊息<BR>> 就算你沒有上網，你的朋友仍可以留下訊息給你，當你上網時就能立即看到，任何 <BR>> 說話都冇走失。<BR>> http://messenger.yahoo.com.hk<BR>> <BR>> <BR>> ------------------------------------------------------------------------<BR>> <BR>> _______________________________________________<BR>> Linuxppc-embedded mailing list<BR>> Linuxppc-embedded@ozlabs.org<BR>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded<BR><BR><BR>-- <BR>Sincerely, <BR>Vitaly<BR></BLOCKQUOTE> <DIV><BR></DIV><BR><BR>Best regards,<br>Chung<p>_______________________________________<br> YM - 離線訊息<br> 就算你沒有上網，你的朋友仍可以留下訊息給你，當你上網時就能立即看到，任何說話都冇走失。<br> http://messenger.yahoo.com.hk