From: "Cedric GROSS" <cg@cgross.info>
To: "'Emmanuel Grumbach'" <egrumbach@gmail.com>
Cc: "'linux-wireless'" <linux-wireless@vger.kernel.org>
Subject: RE: Firmware error for Centrino N 2230
Date: Sun, 14 Jul 2013 11:47:22 +0200 [thread overview]
Message-ID: <000301ce8077$252f1830$6f8d4890$@info> (raw)
In-Reply-To: <CANUX_P2K9_q_FnkzDrn4=Y3rzn3FvkPjCB4qGmts=7kni9oW4A@mail.gmail.com>
Hello Emmanuel,
> De : Emmanuel Grumbach [mailto:egrumbach@gmail.com]
> Envoyé : dimanche 14 juillet 2013 07:03
> À : sedat.dilek@gmail.com
> Cc : Cedric GROSS; linux-wireless
> Objet : Re: Firmware error for Centrino N 2230
>
> >>> > I’m trying to adapt current freebsd driver for supporting my 2230
> >>> NIC.
> >>> >
> >>> > I try to follow ucode command order defined in kernel 3.2 but I
> >>> > reach some difficulties because firmware raise error.
> >>> >
> >>> > Runtime uCode is alive. So far I sent calib result (cmd xB0),
> >>> > configured advanced BT coexistence (cmd x9B,xCC and xCD) running
> >>> > runtime calib (cmd
> >>> > x65) but the command configuring valid chain (cmd x65) failed as
> >>> > the result below :
>
> cmd 0x65? it is not valid chain command.
Yep was typo, it's 0x98.
>
> 1987 means that you haven't sent the Xtal calibration.
Many many many thanks. I will check that tomorrow.
FreeBSD driver for intel wireless card is a bit old and need a lot of
improvement to manage new NIC.
Is there a way to get all assert code meaning ? It could be really a big big
help for me.
Best regards
Cedric
next prev parent reply other threads:[~2013-07-14 9:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 10:12 Firmware error for Centrino N 2230 Cedric GROSS
2013-07-13 11:03 ` Sedat Dilek
2013-07-13 11:15 ` Cedric GROSS
2013-07-13 11:26 ` Sedat Dilek
2013-07-14 5:03 ` Emmanuel Grumbach
2013-07-14 9:47 ` Cedric GROSS [this message]
2013-07-14 10:51 ` Johannes Berg
2013-07-15 8:21 ` Cedric GROSS
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000301ce8077$252f1830$6f8d4890$@info' \
--to=cg@cgross.info \
--cc=egrumbach@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox