Menu
▾
▴
affix-devel — Affix Development Mailing List
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
(12) |
Mar
(7) |
Apr
(12) |
May
(10) |
Jun
(32) |
Jul
(44) |
Aug
(23) |
Sep
(42) |
Oct
(25) |
Nov
(32) |
Dec
(54) |
| 2003 |
Jan
(38) |
Feb
(25) |
Mar
(58) |
Apr
(59) |
May
(53) |
Jun
(78) |
Jul
(44) |
Aug
(4) |
Sep
(9) |
Oct
(4) |
Nov
(2) |
Dec
(8) |
| 2004 |
Jan
(17) |
Feb
(7) |
Mar
(20) |
Apr
(9) |
May
(5) |
Jun
(3) |
Jul
(20) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(7) |
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
(1) |
May
(1) |
Jun
(4) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(3) |
Nov
(2) |
Dec
|
| 2006 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(2) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(1) |
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Shrirang B. <b_s...@ho...> - 2007-10-15 05:45:28
|
Hi Simon, Affix has built-in HCI/L2CAP channels which allow you to send broadcast m= essages See hci.c and l2cap.c which can be used to create userland sockets with affix address family. look for code in CONFIG_AFFIX_L2CAP_GROUPS If I remember correctly socket has to have a bda of zeros, unfortunately = I cannot provide any code. - Shrirang=0A= =0A= [b_s...@ho...]=0A= =0A= =0A= =0A= Real programmers don't comment their code. It was hard to write, it=0A= =0A= should be hard to understand. > Date: Sun, 14 Oct 2007 20:45:53 +0200 > From: sim...@ca... > To: aff...@li... > Subject: [Affix-devel] Sending Broadcasts >=20 > Hi all, >=20 > First, please excuse my bad English, I=B4m from Austria and 17 years old, > so my English isn=B4t the best. >=20 > I=B4m looking for a way to send a broadcast with bluetooth. After hours o= f > searching, I read that its possible to send broadcasts with affix, but I > didn=B4t find further information. >=20 > So please send me some links or a little sample code how it works. >=20 > I need the Broadcast for a project at school. We want to write a program > which=B4ll send the daily time-table to our school mates. On their mobile > phones=B4ll be running a Java program. >=20 > Regards, > Simon >=20 > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Affix-devel mailing list > Aff...@li... > https://lists.sourceforge.net/lists/listinfo/affix-devel _________________________________________________________________ Get the new Windows Live Messenger! http://get.live.com/messenger/overview= |
|
From: <sim...@ca...> - 2007-10-14 18:46:09
|
Hi all, First, please excuse my bad English, I´m from Austria and 17 years old, so my English isn´t the best. I´m looking for a way to send a broadcast with bluetooth. After hours of searching, I read that its possible to send broadcasts with affix, but I didn´t find further information. So please send me some links or a little sample code how it works. I need the Broadcast for a project at school. We want to write a program which´ll send the daily time-table to our school mates. On their mobile phones´ll be running a Java program. Regards, Simon |
|
From: Ilias B. <xyz...@gm...> - 2007-07-02 19:28:20
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <title>Ilias has Tagged you! :)</title> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> </head> <body> <div style="padding: 0 0 10px 30px"><a href="http://www.taggedmail.com/welcome.html?conn=20vi41oha&ect=8ajsfyx&tId=130065&fid=19695a09dadb02de"><img src="http://www.taggedmail.com/imgld.php?img=logo_email_small.gif&ect=8ajsfyx" width="98" height="35" alt="" border="0"></a></div> <table border="0" cellspacing="0" cellpadding="0" width="539"> <tr> <td colspan="3"><img src="http://static.tagged.com/images/invite_crnrrs_topLong.gif" width="539" height="11" alt="" border="0"></td> </tr> <tr> <td align="left" bgcolor="#c9c9c9" width="1"></td> <td width="537" background="http://static.tagged.com/images/invite_gradient.gif" style="font-size: 30px; color: #000000; text-align: center; font-family: Arial, Helvetica, sans-serif; font-weight: bold; background-image: url(http://static.tagged.com/images/invite_gradient.gif); background-repeat: repeat-x; height: 194px;"> <div style="float: left; padding: 15px 10px 0 10px; text-align: left; width:110px; font-size: 13px;"> <img src="http://www.taggedmail.com/imgsrv.php?uid=5376701947" /><br /> <div style="padding:5px 0 0 0;">Ilias B, 35</div> <div style="font-size: 12px; color: red;">Brazil</div> </div> <div style="float: left; width:405px;"> <div style="font-size:16px; padding:0 0 10px 0;">Ilias B has added you as a friend</div> <div style="font-size:20px; margin:0; padding:0 0 15px 0;">Is Ilias B your friend?</div> <a href="http://www.taggedmail.com/welcome.html?conn=20vi41oha&ect=8ajsfyx&tId=130065&fid=19695a09dadb02de&bn=1"><img src="http://static.tagged.com/images/btn_email_yes.gif" width="90" height="44" alt="" border="0" /></a> <a href="http://www.taggedmail.com/welcome.html?conn=20vi41oha&ect=8ajsfyx&tId=130065&fid=19695a09dadb02de&bn=2"><img src="http://static.tagged.com/images/btn_email_no.gif" width="88" height="44" alt="" border="0" /></a> <div style="font-size:16px; padding:20px 0 0 0;">Please respond or Ilias may think you said no :(</div> </div> </td> <td align="right" bgcolor="#c9c9c9" width="1"></td> </tr> <tr> <td colspan="3"><img src="http://static.tagged.com/images/invite_crnrs_bottomShort.gif" width="539" height="11" alt="" border="0"></td> </tr> <tr> <td colspan="3"> <div style="font-size: 12px; font-color: black; font-family: Arial, Helvetica, sans-serif; padding: 10px 0 0 0; text-align: center;"> <a style="color: black" href="http://www.taggedmail.com/no_more.html?unsem=affix-devel%40lists.sourceforge.net&tId=130065&fid=19695a09dadb02de">Click here</a> to block all emails from Tagged, P.O. Box 193152 San Francisco, CA 94119-3152 </div> </td> </tr> </table> </body> </html> <!-- 0nwja --> |
;){kind=link}
|
From: Raphael S. <stu...@gm...> - 2006-12-19 08:13:36
|
Dear List, I tried to install the affix bluetooth module on a linux system with a kernel version 2.6.16. After adding the patches for 2.6.10 (http://sourceforge.net/mailarchive/forum.php?thread_id=8395053&forum_id=5457) there where still some errors. 1. sk_alloc (from net/sock.h) changed the 3 parameter extern struct sock *sk_alloc(int family, gfp_t priority, struct proto *prot, int zero_it); In btcore/af_hci.c and af_l2cap.c i tried to use sock->sk->sk_prot but this failed. 2. skb_unlink (from linux/skbuff.h) has got a new parameter: extern void skb_unlink(struct sk_buff *skb, struct sk_buff_head *list); I don't know if i've used the right lists there. But i can't test it, because module initialisation faild (see first point). 3. in strukt sk_buff (linux/skbuff.h) the field name stamp changed to tstamp. Could anyone solved these problems? Best regards, Raphael Studer |
|
From: Sachin K. <sac...@re...> - 2006-11-03 08:59:28
|
Hi, I have just downloaded the affix source code and want to work on Serial port profile. So want to know the steps involved in this and also the relevant files that I have to go through to understand the working of serial port profile.I really appreciate your help.Thanks,Sachin |
|
From: <Car...@no...> - 2006-07-25 09:31:50
|
Hi Desmond, Unfortunately, Affix is not a BT qualified stack and there is no plans to push affix for qualification in the near future.=20 Br, Carlos >-----Original Message----- >From: aff...@li...=20 >[mailto:aff...@li...] On Behalf=20 >Of ext desmond >Sent: 14 July, 2006 12:53 >To: aff...@li... >Subject: [Affix-devel] Affix BQB qualification > >Dear Sirs, > >The Affix seems to be a very good bluetooth host system.=20 >However, could you kindly suggest if the Affix is BQB qualifed? > > >Rgds >Desmond Yip > |
|
From: desmond <des...@gs...> - 2006-07-14 09:51:30
|
RGVhciBTaXJzLA0KDQpUaGUgQWZmaXggc2VlbXMgdG8gYmUgYSB2ZXJ5IGdvb2QgYmx1ZXRvb3Ro IGhvc3Qgc3lzdGVtLiBIb3dldmVyLCBjb3VsZCB5b3Uga2luZGx5IHN1Z2dlc3QgaWYgdGhlIEFm Zml4IGlzIEJRQiBxdWFsaWZlZD8NCg0KDQpSZ2RzDQpEZXNtb25kIFlpcA== |
|
From: Pradeep S. <pra...@sa...> - 2006-05-17 11:18:57
|
hi -- With Warm Regards, Pradeep Sharma Voice- 09380867694 E-mail- pra...@sa... DISCLAIMER: Information contained and transmitted by this E-MAIL is proprietary to Sahasra Solutions and is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If this is a forwarded message, the content of this E-MAIL may not have been sent with the authority of the Company. If you are not the intended recipient, an agent of the intended recipient or a person responsible for deliveringthe information to the named recipient, you are notified that any use, distribution, transmission, printing, copying or dissemination of this information in any way or in any manner is strictly prohibited. If you have received this communication in error, please delete this mail & notify the sender immediately. |
|
From: ronnie s. <ron...@gm...> - 2006-05-15 10:08:57
|
List, Im Ronnie sahlberg, one of the developers of ethereal. By request of some users I have found an old patch by Christoph Scholz to ethereal for a dissector he wrote for the bluetooth stack in 2002. Christoph's email address unfortunately does not work now after 4 years :-( Since the patch is 4 years old it does not apply to ethereal svn any more since too many internal APIs have changed. I am however massaging and refactoring it for inclusion and have included some of the protocol stack into ethereal already. Ethereal reads the files generated by some tool called 'hcidump' (i am not a bluetooth guy, im a san/nas guy so im not read up on your tools) I am currently refactoring the L2CAP layer and would really benefit from having some more example captures to work and verify with before i check this layer in. In particular I am looking for L2CAP captures containing command packets with InformationRequest/Response, and connectionless reception channel packets. I would also like some captures where the ACL layer contains L2CAP pdus that are fragmented across several ACL packets and a description on how the fragmentation works for bt. This is to start with, to proceed even further I would really benefit from having as many and as large captures as possible to verify with. The more the merrier. Anyone that can provide captures with these kind of packets, and who want me to refactor the patch so that it can all go into mainline ethereal, PLEASE send me such hcidump captures. best regards ronnie sahlberg (I am not subscribed to this list since i am not really that interested in bluetooth but it is a shame to let this patch diverge more than it already has and support for bt would benefit some users. Please send me as many hcidump captures as possible. please) |
|
From: rohit <roh...@af...> - 2006-04-27 11:06:26
|
Hello I am using affix-3.2.0 and linux-kernel-2.6.13 and ported both for arm processor. I am facing a link drop problem in the underline scenario. I have connected a BT Device with my Device under Serial Port profile service and also paired BTHS with my device. In this scenario my device is initiating connection with BTHS and for Serial Port profile it changes the role at the time of connection. I have set Link Supervision time out to 5 secs.when I am giving an outgoing call from my Device connected in the Serial Port profile. Then in that case Link is dropped whle the link between BTHS and called party is established. Thanks in advance for giving valuable suggestion. Thanks & Regds Rohit Sharma |
|
From: rohit <roh...@af...> - 2006-03-17 10:20:16
|
Hi All, I have ported Affix-3.2.0 Stack for Linux 2.6.13 kernel. I am facing a problem at the time of pairing my BT Device with CTP GW device randomly. I have been able to perform pairing with BT Headset with Same piece of Code as many times but face a problem with CTP GW when I am trying to send HCI_AuthenticationRequest command after establishing ACL Link with the device then i receive following Error randomly. After this error I am not able to send any command to my BT device Error Message!!!!!!!! System error: Input/output error (5) in Sending Command Thanks in advance Rohit Sharma |
|
From: rohit <roh...@af...> - 2006-03-17 10:04:07
|
Hi All I have ported affix-3.2.0 stack for linux kernel 2.6.13. I am facing a problem when I am trying to pair/authenticate my device with CTP GW then sometimes everuthing works fine.But at times I receive a System/Input Output error for sending the command HCI_AuthenticationRequest. I have tried pairing with BT Headset and never received this kind of error for running as many times. Error Message shown in as System error: Input/output error (5). Thanks & Regds Rohit Sharma |
|
From: KF (lists) <kf_...@di...> - 2006-02-09 18:24:40
|
Give this patch a shot... for what ever reason it has not been=20 integrated into the main stream code. http://jmedrano.sl-form.com/hid/compile.3.2.0.patch -KF Jose de Jesus Deloya wrote: > I'm a student from the Universidad Autonoma Metropolitana in Mexico,=20 > please I need some help about affix kernel ver. 3.2.0 installing. when=20 > I try to install it, in the compiling step (make all), linux throws=20 > the following messages: > > WARNING: Symbol version dump /usr/src/linux-2.6.13-15/Module.symvers > is missing; modules will have no dependencies and modversion= s. > > CC [M] /usr/src/affix-kernel-3.2.0/btcore/hci.o > In file included from /usr/src/affix-kernel-3.2.0/btcore/hci.c:68: > /usr/src/affix-kernel-3.2.0/include/affix/bluetooth.h: In function=20 > 'btsys_close': > /usr/src/affix-kernel-3.2.0/include/affix/bluetooth.h:1032: error:=20 > implicit declaration of function 'close' > /usr/src/affix-kernel-3.2.0/btcore/hci.c: In function 'affix_sock_reset= ': > /usr/src/affix-kernel-3.2.0/btcore/hci.c:2109: error: 'struct sock'=20 > has no member named 'sk_pair' > /usr/src/affix-kernel-3.2.0/btcore/hci.c: In function 'affix_sock_ready= ': > /usr/src/affix-kernel-3.2.0/btcore/hci.c:2118: error: 'struct sock'=20 > has no member named 'sk_pair' > /usr/src/affix-kernel-3.2.0/btcore/hci.c:2130: error: 'struct sock'=20 > has no member named 'sk_pair' > make[4]: *** [/usr/src/affix-kernel-3.2.0/btcore/hci.o] Error 1 > make[3]: *** [/usr/src/affix-kernel-3.2.0/btcore] Error 2 > make[2]: *** [_module_/usr/src/affix-kernel-3.2.0] Error 2 > make[2]: Leaving directory `/usr/src/linux-2.6.13-15' > make[1]: *** [build] Error 2 > make[1]: Leaving directory `/usr/src/affix-kernel-3.2.0' > make: *** [all] Error 2 > > I don't know why throws that messages, i'm doing my terminal project=20 > and i need to make an aplication to comunicate computers using=20 > bluetooth protocols. > > Thanks for your atention. > > Jos=E9 de Jes=FAs Deloya Cruz |
|
From: Jose de J. D. <jed...@gm...> - 2006-02-03 21:25:02
|
I'm a student from the Universidad Autonoma Metropolitana in Mexico, please
I need some help about affix kernel ver. 3.2.0 installing. when I try to
install it, in the compiling step (make all), linux throws the following
messages:
WARNING: Symbol version dump /usr/src/linux-2.6.13-15/Module.symvers
is missing; modules will have no dependencies and modversions.
CC [M] /usr/src/affix-kernel-3.2.0/btcore/hci.o
In file included from /usr/src/affix-kernel-3.2.0/btcore/hci.c:68:
/usr/src/affix-kernel-3.2.0/include/affix/bluetooth.h: In function
'btsys_close':
/usr/src/affix-kernel-3.2.0/include/affix/bluetooth.h:1032: error: implicit
declaration of function 'close'
/usr/src/affix-kernel-3.2.0/btcore/hci.c: In function 'affix_sock_reset':
/usr/src/affix-kernel-3.2.0/btcore/hci.c:2109: error: 'struct sock' has no
member named 'sk_pair'
/usr/src/affix-kernel-3.2.0/btcore/hci.c: In function 'affix_sock_ready':
/usr/src/affix-kernel-3.2.0/btcore/hci.c:2118: error: 'struct sock' has no
member named 'sk_pair'
/usr/src/affix-kernel-3.2.0/btcore/hci.c:2130: error: 'struct sock' has no
member named 'sk_pair'
make[4]: *** [/usr/src/affix-kernel-3.2.0/btcore/hci.o] Error 1
make[3]: *** [/usr/src/affix-kernel-3.2.0/btcore] Error 2
make[2]: *** [_module_/usr/src/affix-kernel-3.2.0] Error 2
make[2]: Leaving directory `/usr/src/linux-2.6.13-15'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/usr/src/affix-kernel-3.2.0'
make: *** [all] Error 2
I don't know why throws that messages, i'm doing my terminal project and i
need to make an aplication to comunicate computers using bluetooth
protocols.
Thanks for your atention.
Jos=E9 de Jes=FAs Deloya Cruz
|
|
From: Harshad P. <har...@af...> - 2005-11-23 05:47:31
|
I am using linux kernel version 2.6.13 and affix version 3.2.0 but = finding that there are difference in the structure members either they = are not in the appropriate structure or the basic design has also = changed. Kindly advice me. Thanks & Regds Rohit Sharma |
|
From: <roh...@af...> - 2005-11-21 06:31:25
|
Hi,
I have compiled linx 2.6.13 kernel for i386.Now i have compiled affix-3.2.0
kernel for i386.when trying to use
1)insmod affix.o
insmod: error inserting 'affix.o': -1 Invalid module format
2)insmod affix.ko
insmod: error inserting 'affix.ko': -1 Invalid module format
when used
1) file affix.o
affix.o: ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV),
not stripped.
Also checked the gcc used for both linux kernel and affix kernel both
are same.
I am using fedora version 2.6.9 on PC.
Please guide me.Thanks in advance.
Thanks & Regds
Rohit Sharma.
email: roh...@af...
**************************Disclaimer************************************
Information contained in this E-MAIL being proprietary to Aftek Infosys Limited
is 'privileged' and 'confidential' and intended for use only by the individual
or entity to which it is addressed. You are notified that any use, copying
or dissemination of the information contained in the E-MAIL in any manner
whatsoever is strictly prohibited.
***************************************************************************
http://www.aftek.com/
|
|
From: KF (lists) <kf_...@di...> - 2005-10-03 22:02:50
|
Up to kernel 2.6.11 this should work. I had worked out a similar patch
with the help of Carlos. After 2.6.11 the sk_alloc() function changes
which will again break affix.
-KF
Jaime Medrano wrote:
> Hi.
>
> Compilation is broken with kernels newer than 2.6.8.
>
> Attached are patches with fixes for affix-kernel-3.0.0 and
> affix-kernel-3.2.0.
>
> They have been tested with kernel 2.6.10, but should also apply with
> newer kernels.
>
> Regards,
> Jaime.
>
>------------------------------------------------------------------------
>
>--- affix-kernel-3.0.0/include/uart.h 2004-07-29 13:44:58.000000000 +0200
>+++ affix-kernel-3.0.0-jm/include/uart.h 2005-10-01 21:35:23.111982656 +0200
>@@ -231,7 +231,7 @@ static inline unsigned int serial_in(str
> #endif
> case SERIAL_IO_MEM:
> offset <<= btuart->ser.iomem_reg_shift;
>- return readb((unsigned long) btuart->ser.iomem_base + offset);
>+ return readb(btuart->ser.iomem_base + offset);
> default:
> return inb(btuart->ser.port + offset);
> }
>@@ -248,7 +248,7 @@ static inline void serial_out(struct aff
> #endif
> case SERIAL_IO_MEM:
> offset <<= btuart->ser.iomem_reg_shift;
>- writeb(value, (unsigned long) btuart->ser.iomem_base + offset);
>+ writeb(value, btuart->ser.iomem_base + offset);
> break;
> default:
> outb(value, btuart->ser.port + offset);
>diff -up ../affix-kernel-3.2.0/drivers/btuart_tty.c affix-kernel-3.0.0-jm/drivers/btuart_tty.c
>--- affix-kernel-3.0.0/drivers/btuart_tty.c 2004-07-29 13:44:58.000000000 +0200
>+++ affix-kernel-3.0.0-jm/drivers/btuart_tty.c 2005-10-01 19:04:37.000000000 +0200
>@@ -286,7 +286,7 @@ int btuart_tty_write(struct affix_uart *
> DBFENTER;
> //btuart->tty->flags |= (1 << TTY_DO_WRITE_WAKEUP);
> set_bit(TTY_DO_WRITE_WAKEUP, &btuart->tty->flags);
>- actual = btuart->tty->driver->write(btuart->tty, 0, data, size);
>+ actual = btuart->tty->driver->write(btuart->tty, data, size);
> DBFEXIT;
> return actual;
> }
>--- affix-kernel-3.0.0/include/bluetooth.h 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.0.0-jm/include/bluetooth.h 2005-10-02 23:37:18.637975496 +0200
>@@ -789,6 +811,7 @@ int hci_exec_cmd1(int fd, __u16 opcode,
> static inline _syscall3(int,ioctl,int,fd,unsigned int,cmd, void*,arg);
> static inline _syscall3(int,poll,struct pollfd*,ufds,unsigned int,nfds,int,timeout);
> static inline _syscall2(int,socketcall,int,call,unsigned long*,args);
>+static inline _syscall1(int,close,int,fd);
>
> static inline int btsys_socket(int domain, int type, int protocol)
> {
>--- affix-kernel-3.0.0/include/hci.h 2005-10-02 23:47:32.751616032 +0200
>+++ affix-kernel-3.0.0-jm/include/hci.h 2005-10-02 21:43:54.218404504 +0200
>@@ -599,8 +599,10 @@ typedef struct {
> struct list_head q;
>
> struct sock *sk;
>+ struct sock *sk_pair;
> int dport, sport;
> } affix_sock_t;
>+#define affix_sk_pair(sk) (((affix_sock_t*)sk->sk_prot)->sk_pair)
>
> typedef int (*affix_do_connect_t)(struct sock *sk, struct sockaddr_affix *addr);
> typedef void (*affix_do_destroy_t)(struct sock *sk);
>--- affix-kernel-3.0.0/btcore/hci.c 2005-10-02 21:27:07.052516992 +0200
>+++ affix-kernel-3.0.0-jm/btcore/hci.c 2005-10-02 23:35:32.743073968 +0200
>@@ -2106,7 +2106,7 @@ void affix_sock_reset(struct sock *sk, i
> if (!sock_flag(sk, SOCK_DEAD)) {
> sk->sk_state_change(sk);
> }
>- if (sk->sk_pair && destroy) // not owned by the socket yet
>+ if (affix_sk_pair(sk) && destroy) // not owned by the socket yet
> destroy(sk);
> sock_put(sk);
> DBFEXIT;
>@@ -2115,7 +2115,7 @@ void affix_sock_reset(struct sock *sk, i
> int affix_sock_ready(struct sock *sk)
> {
> struct sk_buff *skb;
>- struct sock *pair = sk->sk_pair;
>+ struct sock *pair = affix_sk_pair(sk);
>
> if (sock_flag(pair, SOCK_DEAD))
> return -1;
>@@ -2127,7 +2127,7 @@ int affix_sock_ready(struct sock *sk)
> skb_queue_tail(&pair->sk_receive_queue, skb);
> pair->sk_data_ready(pair, skb->len);
> sock_put(pair); /* put pair, not needed */
>- sk->sk_pair = NULL;
>+ affix_sk_pair(sk) = NULL;
> return 0;
> }
>
>--- affix-kernel-3.0.0/btcore/af_hci.c 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.0.0-jm/btcore/af_hci.c 2005-10-02 21:46:30.099706944 +0200
>@@ -165,10 +165,10 @@ void hpf_destroy(struct sock *sk)
> hcc_close(hsk->con);
> hsk->con = NULL;
> }
>- if (sk->sk_pair) {
>- sk->sk_pair->sk_ack_backlog--;
>- sock_put(sk->sk_pair);
>- sk->sk_pair = NULL;
>+ if (affix_sk_pair(sk)) {
>+ affix_sk_pair(sk)->sk_ack_backlog--;
>+ sock_put(affix_sk_pair(sk));
>+ affix_sk_pair(sk) = NULL;
> }
> if (hsk->flags & AFFIX_FLAGS_CTLMASK)
> affix_ctl_mode &= ~(hsk->flags & AFFIX_FLAGS_CTLMASK);
>@@ -366,7 +366,7 @@ struct sock *hpf_dup(struct sock *osk)
> sk = hpf_create(NULL, PF_AFFIX, GFP_ATOMIC, 1);
> if (!sk)
> return NULL;
>- sk->sk_pair = osk;
>+ affix_sk_pair(sk) = osk;
> sk->sk_protocol = osk->sk_protocol;
> sk->sk_type = osk->sk_type;
> sk->sk_destruct = osk->sk_destruct;
>@@ -434,7 +434,7 @@ int hpf_connect_cfm(hci_con *con, int st
> hsk->con = con;
> hcc_hold(con);
> }
>- if (sk->sk_pair){ /* incomming connection */
>+ if (affix_sk_pair(sk)){ /* incomming connection */
> sock_hold(pair);
> pair->sk_ack_backlog++;
> if (affix_sock_ready(sk) != 0) {
>--- affix-kernel-3.0.0/btcore/af_l2cap.c 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.0.0-jm/btcore/af_l2cap.c 2005-10-02 21:48:22.000000000 +0200
>@@ -142,10 +142,10 @@ int lpf_close(struct sock *sk)
> l2ca_put(lsk->ch);
> lsk->ch = NULL;
> }
>- if (sk->sk_pair) {
>- sk->sk_pair->sk_ack_backlog--;
>- sock_put(sk->sk_pair);
>- sk->sk_pair = NULL;
>+ if (affix_sk_pair(sk)) {
>+ affix_sk_pair(sk)->sk_ack_backlog--;
>+ sock_put(affix_sk_pair(sk));
>+ affix_sk_pair(sk) = NULL;
> }
> /* remove all packets and check if threre is a connection in the queue */
> while((skb = skb_dequeue(&sk->sk_receive_queue)) != NULL) {
>@@ -274,7 +274,7 @@ struct sock *lpf_dup(struct sock *osk)
> if (!sk)
> return NULL;
>
>- sk->sk_pair = osk;
>+ affix_sk_pair(sk) = osk;
> sk->sk_protocol = osk->sk_protocol;
> sk->sk_type = osk->sk_type;
> sk->sk_destruct = osk->sk_destruct;
>@@ -332,7 +332,7 @@ int lpf_connect_cfm(l2cap_ch *ch, int re
> goto err;
> sk->sk_bound_dev_if = ch->hci->devnum;
> lsk->mtu = l2ca_get_mtu(ch);
>- if (sk->sk_pair){ /* incomming connection */
>+ if (affix_sk_pair(sk)){ /* incomming connection */
> if (affix_sock_ready(sk))
> goto err;
> } else if (!sock_flag(sk, SOCK_DEAD)) {
>--- affix-kernel-3.0.0/rfcomm/af_rfcomm.c 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.0.0-jm/rfcomm/af_rfcomm.c 2005-10-02 21:50:58.000000000 +0200
>@@ -212,9 +212,9 @@ int rpf_close(struct sock *sk)
> rfcon_orphan(rsk->con);
> rfcon_put(xchg(&rsk->con, NULL));
> }
>- if (sk->sk_pair) {
>- sk->sk_pair->sk_ack_backlog--;
>- sock_put(xchg(&sk->sk_pair, NULL));
>+ if (affix_sk_pair(sk)) {
>+ affix_sk_pair(sk)->sk_ack_backlog--;
>+ sock_put(xchg(&affix_sk_pair(sk), NULL));
> }
> while((skb = skb_dequeue(&sk->sk_receive_queue)) != NULL) {
> if (skb->sk != sk) {
>@@ -364,7 +364,7 @@ struct sock *rpf_dup(struct sock *osk)
> sk = rpf_create(NULL, PF_AFFIX, GFP_ATOMIC, 1);
> if (!sk)
> return NULL;
>- sk->sk_pair = osk;
>+ affix_sk_pair(sk) = osk;
> sk->sk_protocol = osk->sk_protocol;
> sk->sk_type = osk->sk_type;
> sk->sk_destruct = osk->sk_destruct;
>@@ -434,7 +434,7 @@ int rpf_connect_cfm(rfcomm_con *con, int
> // enable
> rfcon_set_rxfc(con, AFFIX_FLOW_ON);
> }
>- if (sk->sk_pair){ /* incomming connection */
>+ if (affix_sk_pair(sk)){ /* incomming connection */
> if (affix_sock_ready(sk))
> goto err;
> } else if (!sock_flag(sk, SOCK_DEAD)) {
>
>
>
>------------------------------------------------------------------------
>
>--- affix-kernel-3.2.0/include/uart.h 2004-07-29 13:44:58.000000000 +0200
>+++ affix-kernel-3.2.0-jm/include/uart.h 2005-10-01 21:35:23.111982656 +0200
>@@ -231,7 +231,7 @@ static inline unsigned int serial_in(str
> #endif
> case SERIAL_IO_MEM:
> offset <<= btuart->ser.iomem_reg_shift;
>- return readb((unsigned long) btuart->ser.iomem_base + offset);
>+ return readb(btuart->ser.iomem_base + offset);
> default:
> return inb(btuart->ser.port + offset);
> }
>@@ -248,7 +248,7 @@ static inline void serial_out(struct aff
> #endif
> case SERIAL_IO_MEM:
> offset <<= btuart->ser.iomem_reg_shift;
>- writeb(value, (unsigned long) btuart->ser.iomem_base + offset);
>+ writeb(value, btuart->ser.iomem_base + offset);
> break;
> default:
> outb(value, btuart->ser.port + offset);
>diff -up ../affix-kernel-3.2.0/drivers/btuart_tty.c affix-kernel-3.2.0-jm/drivers/btuart_tty.c
>--- affix-kernel-3.2.0/drivers/btuart_tty.c 2004-07-29 13:44:58.000000000 +0200
>+++ affix-kernel-3.2.0-jm/drivers/btuart_tty.c 2005-10-01 19:04:37.000000000 +0200
>@@ -286,7 +286,7 @@ int btuart_tty_write(struct affix_uart *
> DBFENTER;
> //btuart->tty->flags |= (1 << TTY_DO_WRITE_WAKEUP);
> set_bit(TTY_DO_WRITE_WAKEUP, &btuart->tty->flags);
>- actual = btuart->tty->driver->write(btuart->tty, 0, data, size);
>+ actual = btuart->tty->driver->write(btuart->tty, data, size);
> DBFEXIT;
> return actual;
> }
>--- affix-kernel-3.2.0/include/bluetooth.h 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.2.0-jm/include/bluetooth.h 2005-10-02 23:37:18.637975496 +0200
>@@ -789,6 +811,7 @@ int hci_exec_cmd1(int fd, __u16 opcode,
> static inline _syscall3(int,ioctl,int,fd,unsigned int,cmd, void*,arg);
> static inline _syscall3(int,poll,struct pollfd*,ufds,unsigned int,nfds,int,timeout);
> static inline _syscall2(int,socketcall,int,call,unsigned long*,args);
>+static inline _syscall1(int,close,int,fd);
>
> static inline int btsys_socket(int domain, int type, int protocol)
> {
>--- affix-kernel-3.2.0/include/hci.h 2005-10-02 23:47:32.751616032 +0200
>+++ affix-kernel-3.2.0-jm/include/hci.h 2005-10-02 21:43:54.218404504 +0200
>@@ -599,8 +599,10 @@ typedef struct {
> struct list_head q;
>
> struct sock *sk;
>+ struct sock *sk_pair;
> int dport, sport;
> } affix_sock_t;
>+#define affix_sk_pair(sk) (((affix_sock_t*)sk->sk_prot)->sk_pair)
>
> typedef int (*affix_do_connect_t)(struct sock *sk, struct sockaddr_affix *addr);
> typedef void (*affix_do_destroy_t)(struct sock *sk);
>--- affix-kernel-3.2.0/btcore/hci.c 2005-10-02 21:27:07.052516992 +0200
>+++ affix-kernel-3.2.0-jm/btcore/hci.c 2005-10-02 23:35:32.743073968 +0200
>@@ -2106,7 +2106,7 @@ void affix_sock_reset(struct sock *sk, i
> if (!sock_flag(sk, SOCK_DEAD)) {
> sk->sk_state_change(sk);
> }
>- if (sk->sk_pair && destroy) // not owned by the socket yet
>+ if (affix_sk_pair(sk) && destroy) // not owned by the socket yet
> destroy(sk);
> sock_put(sk);
> DBFEXIT;
>@@ -2115,7 +2115,7 @@ void affix_sock_reset(struct sock *sk, i
> int affix_sock_ready(struct sock *sk)
> {
> struct sk_buff *skb;
>- struct sock *pair = sk->sk_pair;
>+ struct sock *pair = affix_sk_pair(sk);
>
> if (sock_flag(pair, SOCK_DEAD))
> return -1;
>@@ -2127,7 +2127,7 @@ int affix_sock_ready(struct sock *sk)
> skb_queue_tail(&pair->sk_receive_queue, skb);
> pair->sk_data_ready(pair, skb->len);
> sock_put(pair); /* put pair, not needed */
>- sk->sk_pair = NULL;
>+ affix_sk_pair(sk) = NULL;
> return 0;
> }
>
>--- affix-kernel-3.2.0/btcore/af_hci.c 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.2.0-jm/btcore/af_hci.c 2005-10-02 21:46:30.099706944 +0200
>@@ -165,10 +165,10 @@ void hpf_destroy(struct sock *sk)
> hcc_close(hsk->con);
> hsk->con = NULL;
> }
>- if (sk->sk_pair) {
>- sk->sk_pair->sk_ack_backlog--;
>- sock_put(sk->sk_pair);
>- sk->sk_pair = NULL;
>+ if (affix_sk_pair(sk)) {
>+ affix_sk_pair(sk)->sk_ack_backlog--;
>+ sock_put(affix_sk_pair(sk));
>+ affix_sk_pair(sk) = NULL;
> }
> if (hsk->flags & AFFIX_FLAGS_CTLMASK)
> affix_ctl_mode &= ~(hsk->flags & AFFIX_FLAGS_CTLMASK);
>@@ -366,7 +366,7 @@ struct sock *hpf_dup(struct sock *osk)
> sk = hpf_create(NULL, PF_AFFIX, GFP_ATOMIC, 1);
> if (!sk)
> return NULL;
>- sk->sk_pair = osk;
>+ affix_sk_pair(sk) = osk;
> sk->sk_protocol = osk->sk_protocol;
> sk->sk_type = osk->sk_type;
> sk->sk_destruct = osk->sk_destruct;
>@@ -434,7 +434,7 @@ int hpf_connect_cfm(hci_con *con, int st
> hsk->con = con;
> hcc_hold(con);
> }
>- if (sk->sk_pair){ /* incomming connection */
>+ if (affix_sk_pair(sk)){ /* incomming connection */
> sock_hold(pair);
> pair->sk_ack_backlog++;
> if (affix_sock_ready(sk) != 0) {
>--- affix-kernel-3.2.0/btcore/af_l2cap.c 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.2.0-jm/btcore/af_l2cap.c 2005-10-02 21:48:22.000000000 +0200
>@@ -142,10 +142,10 @@ int lpf_close(struct sock *sk)
> l2ca_put(lsk->ch);
> lsk->ch = NULL;
> }
>- if (sk->sk_pair) {
>- sk->sk_pair->sk_ack_backlog--;
>- sock_put(sk->sk_pair);
>- sk->sk_pair = NULL;
>+ if (affix_sk_pair(sk)) {
>+ affix_sk_pair(sk)->sk_ack_backlog--;
>+ sock_put(affix_sk_pair(sk));
>+ affix_sk_pair(sk) = NULL;
> }
> /* remove all packets and check if threre is a connection in the queue */
> while((skb = skb_dequeue(&sk->sk_receive_queue)) != NULL) {
>@@ -279,7 +279,7 @@ struct sock *lpf_dup(struct sock *osk)
> if (!sk)
> return NULL;
>
>- sk->sk_pair = osk;
>+ affix_sk_pair(sk) = osk;
> sk->sk_protocol = osk->sk_protocol;
> sk->sk_type = osk->sk_type;
> sk->sk_destruct = osk->sk_destruct;
>@@ -344,7 +344,7 @@ int lpf_connect_cfm(l2cap_ch *ch, int re
> #else
> lsk->mtu = l2ca_get_mtu(ch);
> #endif
>- if (sk->sk_pair){ /* incomming connection */
>+ if (affix_sk_pair(sk)){ /* incomming connection */
> if (affix_sock_ready(sk))
> goto err;
> } else if (!sock_flag(sk, SOCK_DEAD)) {
>--- affix-kernel-3.2.0/rfcomm/af_rfcomm.c 2004-05-17 20:21:55.000000000 +0200
>+++ affix-kernel-3.2.0-jm/rfcomm/af_rfcomm.c 2005-10-02 21:50:58.000000000 +0200
>@@ -212,9 +212,9 @@ int rpf_close(struct sock *sk)
> rfcon_orphan(rsk->con);
> rfcon_put(xchg(&rsk->con, NULL));
> }
>- if (sk->sk_pair) {
>- sk->sk_pair->sk_ack_backlog--;
>- sock_put(xchg(&sk->sk_pair, NULL));
>+ if (affix_sk_pair(sk)) {
>+ affix_sk_pair(sk)->sk_ack_backlog--;
>+ sock_put(xchg(&affix_sk_pair(sk), NULL));
> }
> while((skb = skb_dequeue(&sk->sk_receive_queue)) != NULL) {
> if (skb->sk != sk) {
>@@ -364,7 +364,7 @@ struct sock *rpf_dup(struct sock *osk)
> sk = rpf_create(NULL, PF_AFFIX, GFP_ATOMIC, 1);
> if (!sk)
> return NULL;
>- sk->sk_pair = osk;
>+ affix_sk_pair(sk) = osk;
> sk->sk_protocol = osk->sk_protocol;
> sk->sk_type = osk->sk_type;
> sk->sk_destruct = osk->sk_destruct;
>@@ -434,7 +434,7 @@ int rpf_connect_cfm(rfcomm_con *con, int
> // enable
> rfcon_set_rxfc(con, AFFIX_FLOW_ON);
> }
>- if (sk->sk_pair){ /* incomming connection */
>+ if (affix_sk_pair(sk)){ /* incomming connection */
> if (affix_sock_ready(sk))
> goto err;
> } else if (!sock_flag(sk, SOCK_DEAD)) {
>
>
>
|
|
From: Jaime M. <ove...@eu...> - 2005-10-03 19:48:42
|
Hi. Compilation is broken with kernels newer than 2.6.8. Attached are patches with fixes for affix-kernel-3.0.0 and affix-kernel-3.2.0. They have been tested with kernel 2.6.10, but should also apply with newer kernels. Regards, Jaime. |
|
From: Jaime M. <ove...@gm...> - 2005-10-03 19:39:37
|
Hi. Compilation is broken with kernels newer than 2.6.8. Attached are patches with fixes for affix-kernel-3.0.0 and affix-kernel-3.2.0. They have been tested with kernel 2.6.10, but should also apply with newer kernels. Regards, Jaime. |
|
From: <Car...@no...> - 2005-08-26 15:17:28
|
Hi everyone ! Again we have a security update for affix package.:( This time Kevin Finisterre has found a popen() exploit in btsrv, when it = is managing a pin request (if you have that option disable you should be = safe. However, I strongly encourage to patch the btsrv anyway !!!) Please, go to the affix web page an download the patch that fixes this. =20 Br, Carlos Chinea P.S: Thanks Kevin for the feedback ! |
|
From: Al <Al_...@is...> - 2005-07-08 06:18:37
|
Hi,
Thanks for reply.
I'm trying Affix and below steps are what I've done:
1. Remove BlueZ support and recompile kernel and modules.
2. Reboot use new kernel and modules, no BlueZ support.
3. Install Affix Kernel for 2.6. Installation seems OK.
4. Install Affix Utilities for 2.6. First, ./configure, then
when doing make, resulting the following error messages:
-------------------------------------------------------------------------=
-------
gcc -O2 -Wall -Wstrict-prototypes -fomit-frame-pointer -pipe -o =
.libs/btftp
btftp.o ../utils/.libs/libaffix_utils.so
../obex/.libs/libaffix_obex.so -lopenobex -lreadline
../lib/.libs/libaffix.so -Wl,--rpath -Wl,/usr/local/lib
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `tgetnum'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `tgoto'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `tgetflag'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `BC'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `tputs'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `PC'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `tgetent'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `UP'
/usr/lib/gcc-lib/i386-redhat-linux/3.3.3/../../../libreadline.so: =
undefined
reference to `tgetstr'
collect2: ld returned 1 exit status
make[1]: *** [btftp] Error 1
make[1]: Leaving directory `/root/download/affix/affix-3.2.0/control'
make: *** [all-recursive] Error 1
-------------------------------------------------------------------------=
----
I also found FAQ has the similiar issue. But I have no idea how to =
do
it. Can anyone help with this error?
FAQ:
-------------------------------------------------------------------------=
-------
Compiling Affix 3.0 utilities on Gentoo produces lots of
"/lib/libreadline.so: undefined reference to `XXX'" error messages?
The problem can be solved by compiling libreadline with libncurses.
-------------------------------------------------------------------------=
------
thanks a lot,
Al
-----Original Message-----=20
From: karthik.bala [mailto:kar...@sa...]=20
Sent: 2005/6/24 [=ACP=B4=C1=A4=AD] =A4U=A4=C8 03:51=20
To: Al; aff...@li...=20
Cc:=20
Subject: RE: [Affix-devel] Install affix Kernel
=09
=09
Yeah,
Hope you have affix alone now !!
=09
Karthik bala guru
=09
-----Original Message-----
From: aff...@li...
[mailto:aff...@li...] On Behalf Of Al Chane
Sent: Friday, June 24, 2005 4:33 PM
To: aff...@li...
Subject: [Affix-devel] Install affix Kernel
=09
=09
Hi, there:
=09
I am not sure the orders of installing affix kernel with linux
kernel
Since Affix needs to remove BlueZ support first.
=09
Here is what I do:
=09
1. configure kernel first: make menuconfig
->do as End user Manual steps.
=09
2. build kenel and modules: make dep;make clean; make bzImage;make
modules;make modules_install
=09
3. Then install Affix kernel.
=09
Is the order correct?
=09
Thanks a lot,
=09
Al
=09
=09
=09
=09
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. =
http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dclick
_______________________________________________
Affix-devel mailing list
Aff...@li...
https://lists.sourceforge.net/lists/listinfo/affix-devel
=09
=09
=09
|
|
From: <Car...@no...> - 2005-07-06 15:08:16
|
Hi everyone ! We have a security patch release for Affix package. The security patch fixes two security threats in the File Transfer = Profile.=20 Many thanks to Kevin Finisterre for his feedback about the latest = security issues in affix. Please, stay tune to affix, there is new things coming ! ;) Br, Carlos Chinea =20 |
|
From: Annamalai P. <apr...@ta...> - 2005-06-24 12:35:19
|
Hi List,
I would like to use affix with hands free profile .... is there
any documentation which explains hfp API's. I have downloaded
affix-kernel-3.2.0 version for 2.6 kernel and affix also ..
Thanks
Prakash
|
|
From: karthik.bala <kar...@sa...> - 2005-06-24 07:51:38
|
Yeah,
Hope you have affix alone now !!
Karthik bala guru
-----Original Message-----
From: aff...@li...
[mailto:aff...@li...] On Behalf Of Al Chane
Sent: Friday, June 24, 2005 4:33 PM
To: aff...@li...
Subject: [Affix-devel] Install affix Kernel
Hi, there:
I am not sure the orders of installing affix kernel with linux
kernel
Since Affix needs to remove BlueZ support first.
Here is what I do:
1. configure kernel first: make menuconfig
->do as End user Manual steps.
2. build kenel and modules: make dep;make clean; make bzImage;make
modules;make modules_install
3. Then install Affix kernel.
Is the order correct?
Thanks a lot,
Al
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Affix-devel mailing list
Aff...@li...
https://lists.sourceforge.net/lists/listinfo/affix-devel
|
|
From: Al C. <al_...@is...> - 2005-06-24 07:33:34
|
Hi, there:
I am not sure the orders of installing affix kernel with linux kernel
Since Affix needs to remove BlueZ support first.
Here is what I do:
1. configure kernel first: make menuconfig
->do as End user Manual steps.
2. build kenel and modules: make dep;make clean; make bzImage;make
modules;make modules_install
3. Then install Affix kernel.
Is the order correct?
Thanks a lot,
Al
|
51 messages has been excluded from this view by a project administrator.
