Did Mindready go out of business?

Adam Mallory wrote:

John Nagle wrote:

Well, actually this is about a technical problem with a QNX-specific
device driver kit. The Mindready Low Level Adapter library is a library
to assist in the development of drivers for FireWire devices for QNX.


Sorry John, I must of misunderstood. Which QNX DDK product, with which
you are experiencing problems, are you referencing in your initial post?

It’s a device driver kit from one of QSSL’s strategic partners. See

http://www.qnx.com/partners/partner.html?partnerid=161300

John Nagle
Team Overbot

John Nagle <nagle@downside.com> wrote:

Adam Mallory wrote:
John Nagle wrote:

Well, actually this is about a technical problem with a QNX-specific
device driver kit. The Mindready Low Level Adapter library is a library
to assist in the development of drivers for FireWire devices for QNX.


Sorry John, I must of misunderstood. Which QNX DDK product, with which
you are experiencing problems, are you referencing in your initial post?

It’s a device driver kit from one of QSSL’s strategic partners. See

http://www.qnx.com/partners/partner.html?partnerid=161300

I think there is a misunderstanding here: whether the newsgroup
“qnx.ddk” is for QNX (as company)'s own DDK, or any DDK that is for QNX
(as an OS).

Frank

“Frank Liu” <fliu@usdjmp1.eng.vodafone-us.com> wrote in message
news:dg720q$ioi$1@inn.qnx.com

John Nagle <> nagle@downside.com> > wrote:
Adam Mallory wrote:
John Nagle wrote:

Well, actually this is about a technical problem with a QNX-specific
device driver kit. The Mindready Low Level Adapter library is a
library
to assist in the development of drivers for FireWire devices for QNX.


Sorry John, I must of misunderstood. Which QNX DDK product, with which
you are experiencing problems, are you referencing in your initial post?

It’s a device driver kit from one of QSSL’s strategic partners. See

http://www.qnx.com/partners/partner.html?partnerid=161300

I think there is a misunderstanding here: whether the newsgroup
“qnx.ddk” is for QNX (as company)'s own DDK, or any DDK that is for QNX
(as an OS).

There is a newsgroup with the prefix 3rd party (although it’s for product
announcement).
I wouldn’t expect QSS to provide space for 3rd party product support, nor
would I expect
MindReady to provide space to discuss QNX filesystem issue…

Frank

Mario Charest wrote:

“Frank Liu” <> fliu@usdjmp1.eng.vodafone-us.com> > wrote in message
news:dg720q$ioi$> 1@inn.qnx.com> …

John Nagle <> nagle@downside.com> > wrote:

Adam Mallory wrote:

John Nagle wrote:


Well, actually this is about a technical problem with a QNX-specific
device driver kit. The Mindready Low Level Adapter library is a
library
to assist in the development of drivers for FireWire devices for QNX.


Sorry John, I must of misunderstood. Which QNX DDK product, with which
you are experiencing problems, are you referencing in your initial post?

It’s a device driver kit from one of QSSL’s strategic partners. See

http://www.qnx.com/partners/partner.html?partnerid=161300

I think there is a misunderstanding here: whether the newsgroup
“qnx.ddk” is for QNX (as company)'s own DDK, or any DDK that is for QNX
(as an OS).


There is a newsgroup with the prefix 3rd party (although it’s for product
announcement).
I wouldn’t expect QSS to provide space for 3rd party product support, nor
would I expect
MindReady to provide space to discuss QNX filesystem issue…

Just my $0.02, but I would suggested comp.os.qnx as the place to go. It is a
general purpose QNX newsgroup that is not run by QNX. All the qnx.* groups are
provided by QNX for the purpose of supporting their RTOS.

K.

“Kevin N” <xxxx@yyyy.com> wrote in message news:dg769u$ls7$1@inn.qnx.com

Sorry John, I must of misunderstood. Which QNX DDK product, with which
you are experiencing problems, are you referencing in your initial
post?

It’s a device driver kit from one of QSSL’s strategic partners. See

http://www.qnx.com/partners/partner.html?partnerid=161300

I think there is a misunderstanding here: whether the newsgroup
“qnx.ddk” is for QNX (as company)'s own DDK, or any DDK that is for QNX
(as an OS).


There is a newsgroup with the prefix 3rd party (although it’s for product
announcement).
I wouldn’t expect QSS to provide space for 3rd party product support, nor
would I expect
MindReady to provide space to discuss QNX filesystem issue…

Just my $0.02, but I would suggested comp.os.qnx as the place to go. It is
a general purpose QNX newsgroup that is not run by QNX. All the qnx.*
groups are provided by QNX for the purpose of supporting their RTOS.

This is an artifical distinction. Even if QNX provides this forum, they
can’t stop people from saying whatever they consider relevant. In Russia
drivers blink their high-beam lights to oncoming traffic to warn about
traffic police ambushes ahead. Federal government might consider this misuse
of the roads (they weren’t built for that purpose, right?) but people might
think the government can stuff it.

What John did was essentially a high-beam blink to warn people about the
situation they might face with HW-locked software in general and Mindready
QNX DDK in particular. Since a lot of potential ‘drivers’ (developers) would
drive down this ‘road’ (qnx.ddk) it is as good place as any to warn them.
Whether QNX as a company likes it or not is not relevant.

Personally I strongly suspect that the fact QNX still has no FireWire
support of its own has to do with some behind-the-scenes agreement between
them and their ‘strategic partner’ MindReady. If this discussion draws the
ire of MindReady and QNX by undermining that agreement, it’s for the better.
Maybe MindReady will realize that HW-locking is bad idea. And maybe QNX will
realize they need to either work with some HW vendors on support or write
drivers themselves if they want to be considered for projects that require
video feed.

– igor

Igor Kovalenko wrote:

Personally I strongly suspect that the fact QNX still has no FireWire
support of its own…

QSSL might want to buy the QNX Firewire stack product
line from Mindready. Mindready is moving in other directions,
and QNX needs Firewire support.

Having written a video driver using the Mindready LLA, I
can report that it’s an adequate way to talk to Firewire
controllers. It really is very low level; it lets you
send and receive packets on a Firewire network, but you
have to write your own device recognition, hot-plugging support,
and device handlers. Mindready has some higher level protocols
that run above the basic LLA level, but I didn’t use them.

(Incidentally, Firewire is really a local area network, even
though it’s popularly called a “bus”. At the driver level, it
looks more like an Ethernet controller than a bus interface,
with network-controller type packet queueing. There’s even
multicasting.)

John Nagle
Team Overbot

Igor Kovalenko wrote:

“Kevin N” <> xxxx@yyyy.com> > wrote in message news:dg769u$ls7$> 1@inn.qnx.com> …



Just my $0.02, but I would suggested comp.os.qnx as the place to go. It is
a general purpose QNX newsgroup that is not run by QNX. All the qnx.*
groups are provided by QNX for the purpose of supporting their RTOS.



This is an artifical distinction. Even if QNX provides this forum, they
can’t stop people from saying whatever they consider relevant.

Sure they can. Many web-based discussion forums on the Internet are provided at
the discretion of the owners of the web site. Many do police their own sites
(with deputies called “Moderators”) and censor the discussions going on. This
ranges from removing material that they may worry about being illegal (and thus
don’t want to host on their site) to squelching flame wars. While such
discussion forums are public in the sense that pretty much anyone can join and
post, they are still owned by someone (or corporate entity) that can pretty much
do whatever they want with it.

The only distinction between the qnx.* newsgroups and these web-based forums is
the medium: NNTP vs. HTTP. Unlike the comp.os.qnx newsgroup, I believe the qnx.*
groups are provided by QNX itself and only via inn.qnx.com. Sure, anyone can
subscribe and post, but since QNX hosts and owns these groups, I think they can
do pretty much whatever they want. Now whether they choose to exercise this
level of control is entirely up to them - thus far I haven’t seen any evidence
of them doing so.

comp.os.qnx is not owned by QNX. It may be available via inn.qnx.com, presumably
as a courtesy to their customers, but they don’t own it in any way. The group
can be accessed from many other NNTP servers and even via web interfaces
(groups.google.com).


In Russia
drivers blink their high-beam lights to oncoming traffic to warn about
traffic police ambushes ahead. Federal government might consider this misuse
of the roads (they weren’t built for that purpose, right?) but people might
think the government can stuff it.

I think a better comparision is to a privately owned newspaper. The publisher is
free to publish whatever articles and letters to the editor that they choose.
They can’t do anything about you exercising your freedom of speech elsewhere,
but they certainly don’t have to publish your letter to the editor.

BTW, I’ve actually heard (though I’ve never had it verified) that it is illegal
in many places to warn other motorists of speed traps ahead. Of course, that
doesn’t mean people don’t do it. :slight_smile:



What John did was essentially a high-beam blink to warn people about the
situation they might face with HW-locked software in general and Mindready
QNX DDK in particular. Since a lot of potential ‘drivers’ (developers) would
drive down this ‘road’ (qnx.ddk) it is as good place as any to warn them.

I don’t disagree with this at all. I think the information John is providing is
very useful. All I am suggesting is to use a medium that is not owned by QNX to
raise these issues.

K.

“Kevin N” <xxxx@yyyy.com> wrote in message news:dg974a$79o$1@inn.qnx.com

This is an artifical distinction. Even if QNX provides this forum, they
can’t stop people from saying whatever they consider relevant.

Sure they can. Many web-based discussion forums on the Internet are
provided at the discretion of the owners of the web site. Many do police
their own sites (with deputies called “Moderators”) and censor the
discussions going on. This ranges from removing material that they may
worry about being illegal (and thus don’t want to host on their site) to
squelching flame wars. While such discussion forums are public in the
sense that pretty much anyone can join and post, they are still owned by
someone (or corporate entity) that can pretty much do whatever they want
with it.

Yeah. But that begs a question - would not the staff time spent on censoring
their newsgroups be better applied to fixing the problem that made people
talk in the first place? Writing a firewire stack perhaps?


What John did was essentially a high-beam blink to warn people about the
situation they might face with HW-locked software in general and
Mindready QNX DDK in particular. Since a lot of potential ‘drivers’
(developers) would drive down this ‘road’ (qnx.ddk) it is as good place
as any to warn them.

I don’t disagree with this at all. I think the information John is
providing is very useful. All I am suggesting is to use a medium that is
not owned by QNX to raise these issues.

In general sense, yes. But QNX is so well known for unwillingness/inability
to react to more subtle signs that their market/customers send them, it
often takes a sledgehammer to make a hint.

Let’s state it again - this is a TECHNICAL support newsgroup.

The people here that read these groups have no say in product direction, licensing or any of the other complaints you are airing. They are are either support staff or interested developers.

The only effect of your complaints are to make us, the techies, personally feel bad, and
stressed.

qnx.cafe was created for people to rant in, or to talk about non technical issues.

That said, I can see John’s point, he had a problem with a ddk from one of our partners
and he started off just asking about question of the community in general. So fair enough.

Plus he’s in a very stressful period of an incredibly cool project. I hope it didn’t
mess things up too much.

Also Igor, if you think we have ANY spare time, you are grossly mistaken. I think one
of the reasons for the drop off in qnx developer invovlement in the community is actually
more that they just don’t have the mental space to work on anything else right now…

Igor Kovalenko wrote:

“Kevin N” <> xxxx@yyyy.com> > wrote in message news:dg974a$79o$> 1@inn.qnx.com> …

This is an artifical distinction. Even if QNX provides this forum, they
can’t stop people from saying whatever they consider relevant.

Sure they can. Many web-based discussion forums on the Internet are
provided at the discretion of the owners of the web site. Many do police
their own sites (with deputies called “Moderators”) and censor the
discussions going on. This ranges from removing material that they may
worry about being illegal (and thus don’t want to host on their site) to
squelching flame wars. While such discussion forums are public in the
sense that pretty much anyone can join and post, they are still owned by
someone (or corporate entity) that can pretty much do whatever they want
with it.


Yeah. But that begs a question - would not the staff time spent on censoring
their newsgroups be better applied to fixing the problem that made people
talk in the first place? Writing a firewire stack perhaps?



What John did was essentially a high-beam blink to warn people about the
situation they might face with HW-locked software in general and
Mindready QNX DDK in particular. Since a lot of potential ‘drivers’
(developers) would drive down this ‘road’ (qnx.ddk) it is as good place
as any to warn them.

I don’t disagree with this at all. I think the information John is
providing is very useful. All I am suggesting is to use a medium that is
not owned by QNX to raise these issues.



In general sense, yes. But QNX is so well known for unwillingness/inability
to react to more subtle signs that their market/customers send them, it
often takes a sledgehammer to make a hint.
\


cburgess@qnx.com

Colin Burgess wrote:

Let’s state it again - this is a TECHNICAL support newsgroup.
That said, I can see John’s point, he had a problem with a ddk from one
of our partners
and he started off just asking about question of the community in
general. So fair enough.

Plus he’s in a very stressful period of an incredibly cool project. I
hope it didn’t
mess things up too much.

Ir cost us time we didn’t have, and as a result, the visual
road follower wasn’t working during key field tests.
It will probably be less effective as a result.

The group postings were helpful in escalating the issue
with Mindready, where the postings were definitely noticed. There
were some substantial problems up front reaching technical
support, problems severe enough that we thought the company
had ceased operations. So this wasn’t just venting.

Sometimes you just have to apply a sizable clue stick to
a vendor.

Anyway, enough on this subject. Thanks, everyone.

John Nagle
Team Overbot

“Colin Burgess” <cburgess@qnx.com> wrote in message
news:dg9um9$li5$1@inn.qnx.com

Also Igor, if you think we have ANY spare time, you are grossly mistaken.
I think one
of the reasons for the drop off in qnx developer invovlement in the
community is actually
more that they just don’t have the mental space to work on anything else
right now…

I wish I could believe that, but alas, I’ve never believed into the ‘not
enough time’ thing. It is well known phenomena that any gives task consumes
all the time available. People do what is close to their hearts no matter
how busy. If they don’t that’s more likely to mean it’s not that close
anymore. A lot of people who had that flame in them got burned out by
frustration and left. Both inside and outside of QNX.

Makes me wonder though, what it is that QNX is so busy with these days.
There has not been any major feature development in years. Hardware support
is stagnating and getting to the point of being as bad as it was in late
QNX4 days. Major problems/deficiencies that we’ve been talking about for
years are still there.