In message <[EMAIL PROTECTED]> Julian Elischer writes:
: whichever card is in the top slot (2nd slot I think) doesn't work.
Noted. I don't have a laptop with two slots to test with :-(.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
With my inspiron:
cvsupped Tues. Evening PDT.
pci_cfgintr_unique: hard-routed to irq 11
pci_cfgintr: 0:4 INTA routed to irq 11
pcic0: irq 11 at device 4.0 on pci0
pcic0: Memory mapped device, will work.
pcic0: PCI Memory allocated: 0x4400
pcic0: TI12XX PCI Config Reg: [ring enable][speaker e
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: I make a short patch to sharing IRQ between a PCIC and a PC Card when using
: PCI IRQ routing.
: #Does this patch help you?
Yes. I've made a larger patch and committed it that mostly works
without changes (you still need to add -I, but n
In message <[EMAIL PROTECTED]> [EMAIL PROTECTED] writes:
: I make a short patch to sharing IRQ between a PCIC and a PC Card when using
: PCI IRQ routing.
: #Does this patch help you?
Yes. It does. Thank you!
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curr
I make a short patch to sharing IRQ between a PCIC and a PC Card when using
PCI IRQ routing.
#Does this patch help you?
---
YAMAMOTO ShigeruInternet Initiative Japan Inc.
<[EMAIL PROTECTED]> Network Engineering Div.
Index: pcic.c
In message <[EMAIL PROTECTED]> Samuel Tardieu writes:
: fine by adding "-I -i 9". It seems to be only my Psion Dacom Gold Card
: that has a problem.
OK. This is the second report of a modem failing (but mine worked,
grump) so I'll look into this some more.
Warner
To Unsubscribe: send mail to [
In message <[EMAIL PROTECTED]> Samuel Tardieu writes:
: I just did that. I got a panic, which I could not save (I cannot panic
: From=20ddb, it just doesn't work). ddb reports the faulty process as
: being ddb, and it relates to "trap 12 being called ..." (I don't
: remember the exact message unfo
> "Sam" == Samuel Tardieu <[EMAIL PROTECTED]> writes:
Sam> I just did that. I got a panic, which I could not save (I cannot
Sam> panic From ddb, it just doesn't work). ddb reports the faulty
Sam> process as being ddb, and it relates to "trap 12 being called
Sam> ..." (I don't remember the exa
> "Warner" == Warner Losh <[EMAIL PROTECTED]> writes:
Warner> In summary:
Warner> o Use the same config file you used before.
Warner> o Update pccardd
Warner> o Add "-I -i 9" to pccardd_flags (if your pcic's irq is 9).
Warner> o rebuild and reinstall the kernel.
Warner> o reboot. Send your p
Quoting Warner Losh <[EMAIL PROTECTED]>:
>
>
> If you have device pccard rather than card in your kernel, you are
> running NEWCARD.
I know but I couldn't get it to run with pccardd. I'm going to try again
tomorrow although it has been working great:-)
>
> Also, do you have one slot or two?
In message <[EMAIL PROTECTED]> Edwin Culp writes:
: The kernel configuration that I couldn't get to work was basically GENERIC with
: SCSI, USB commented out and IPFW added. The one that works is the NEWCARD with
: almost identical but with the following differences only, I think.
:
: #device
In message <[EMAIL PROTECTED]> Samuel Tardieu writes:
: I think that a short HOWTO-UPGRADE would benefit to everyone. For
The entry in UPDATING should do that. If it is unclear, let me know
and I'll update it.
: example, should I:
:
: - keep my old kernel settings (using the glue compatibili
The kernel configuration that I couldn't get to work was basically GENERIC with
SCSI, USB commented out and IPFW added. The one that works is the NEWCARD with
almost identical but with the following differences only, I think.
#device card# pccard bus
#device pcic
> "Warner" == Warner Losh <[EMAIL PROTECTED]> writes:
Warner> You shouldn't have had to do that. which ones were they, and
Warner> are you still running pccard (classic) aka OLDCARD?
Warner,
I think that a short HOWTO-UPGRADE would benefit to everyone. For
example, should I:
- keep my o
In message <[EMAIL PROTECTED]> Edwin Culp writes:
: I also had to add options from NEWCARD to my kern cofiguration file.
: That is why I couldn't get it to work with my GENERIC based configuration.
: I haven't seen that documented, but it worked for me after 3 days of
: suffering.
You shouldn't
I also had to add options from NEWCARD to my kern cofiguration file.
That is why I couldn't get it to work with my GENERIC based configuration.
I haven't seen that documented, but it worked for me after 3 days of suffering.
ed
Quoting Warner Losh <[EMAIL PROTECTED]>:
> In message <[EMAIL PROTE
In message <[EMAIL PROTECTED]> Brian Somers writes:
: With a ? instead of the 9 on the config line, I got an irq resource
: allocation failure. Go figure !
Add -I to pccardd_flags.
warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mess
I got the same results as you. It eventually worked when I copied
the entry matching my card into /etc/pccard.conf and hard-wired the
irq as the same as the pcic device (9 in my case):
$ cat /etc/pccard.conf
irq 9
card "Lucent Technologies" "WaveLAN/IEEE"
config auto "wi" 9
In message <[EMAIL PROTECTED]> Seth Kingsley writes:
: Sorry, I guess maybe this directive is counter-intuative. It supposed to
: be a list of the free irq's in the system for pccardd to use with
: inserted pccards when configuring them. Trying to use the irq that the
: cardbus bridge already has
In message <[EMAIL PROTECTED]> Julian Elischer writes:
: Failed to allocate IRQ for Linksys
Add -I to your pccardd_flags in rc.conf. Others have suggested '-I -i
11' for your case.
Also, it is very important that you install a new pccardd too.
Otherwise, you may find your system hanging when t
So the question remains..
where was I supposed to change the interrupt mentionned in the
UPDATING entry..
if not in the pccard.conf, then where?
I certainly get the 'hangs' mentionned as being a symptom
of NOT doing it..
Warner?
On Fri, 8 Jun 2001, Mike Smith wrote:
> > On Fri, Jun 08, 2001 a
> On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote:
> > kernel: pcic1: irq 11 at device 4.1 on pci0
>
> > in pccard.conf I had
> >
> > irq 11
> >
> > is this not what I was supposed to do?
>
> Sorry, I guess maybe this directive is counter-intuative. It supposed to
> be a list
On Fri, Jun 08, 2001 at 01:55:40PM -0700, Seth Kingsley wrote:
> On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote:
> > kernel: pcic1: irq 11 at device 4.1 on pci0
>
> > in pccard.conf I had
> >
> > irq 11
> >
> > is this not what I was supposed to do?
>
> Sorry, I guess maybe t
On Fri, Jun 08, 2001 at 11:19:10AM -0700, Julian Elischer wrote:
> kernel: pcic1: irq 11 at device 4.1 on pci0
> in pccard.conf I had
>
> irq 11
>
> is this not what I was supposed to do?
Sorry, I guess maybe this directive is counter-intuative. It supposed to
be a list of the free irq's in t
I upgraded to last nights's -current.
UPGRADING said:
20010604:
pccard support for pci cards has been committed. You must change
your /etc/pccard.conf irq lines. It must match the irq used by
pcic device. Interrupt storms may result if you fail to do this.
Inter
25 matches
Mail list logo
